You are viewing a single thread.
View all comments View context
-9 points
*

That’s not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.

permalink
report
parent
reply
91 points

I don’t know the history of column span but the reason Firefox was “behind” on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.

It was Google doing their variation of “embrace, extend, extinguish”

It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.

permalink
report
parent
reply
8 points

Google was actually later to implement this particular standard than Edge and Safari, at least according to MDN. And I believe this was before Chredge.

permalink
report
parent
reply
6 points

Chredge :D

permalink
report
parent
reply
24 points

I’m gonna be honest, if they used a feature that wasn’t ready for prime time, it’s still on them.

permalink
report
parent
reply
3 points
*

Totally agree. It’s not the fault of Firefox at all. This is just being trigger-happy on new standards before they are ready and unwillingness to fix a problem in a different way.

permalink
report
parent
reply
-4 points

It got added because it worked extremely well on browsers that implemented it, and it solved a problem that was needed on the site in question, which was very difficult to solve otherwise. I can’t blame a site for using an open standard that works for a majority of its users and which makes the development effort significantly less.

permalink
report
parent
reply
0 points

You don’t change standards to fix bad code

permalink
report
parent
reply
5 points
*

This was due to Firefox at the time not implementing web standards that Chrome did.

Uhm, yeah, that’s what browsers do. There are somewhere about 150 web standards and some are hard requirement while others are soft. Blink has some implemented that Webkit hasn’t but Gecko has and that’s true for all three. Same for browsers.

Btw, the one with the most implemented standards is QtWebkit by far. It’s still slower tho.

permalink
report
parent
reply
5 points

Yeah? I’m not saying there’s anything wrong with that. I’m saying it’s bullshit to say a developer has done a crap job when one browser doesn’t implement a web standard that is perfect tailor-made for their site’s use case.

permalink
report
parent
reply
1 point

Still a bad job tho, if his implementation requires things that aren’t common and has no workarounds in place.

permalink
report
parent
reply
0 points
*

If your job is to make websites and you make sites that don’t work on a browser that has over 100 million users you’re not doing your job.

permalink
report
parent
reply
1 point

If only one browser runs it, it’s not a standard

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 7.1K

    Monthly active users

  • 1.2K

    Posts

  • 41K

    Comments