Firefox

17602 readers

628 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml

1379

How about no? (sh.itjust.works)

submitted 8 months ago by ratman150@sh.itjust.works to c/firefox@lemmy.ml

139 comments fedilink hide all child comments

Everything worked perfectly as it always does.

you are viewing a single comment's thread
view the rest of the comments

[–] d_k_bo@feddit.de 14 points 8 months ago (1 children)

There is no uniform "HTML version", "JavaScript version" or "CSS version" that describes which web APIs are implemented. Browser engines support some features that others don't support and vice versa.

[–] reddig33@lemmy.world 7 points 8 months ago* (last edited 8 months ago)

Maybe that’s the problem though. W3C and their ilk needs to define which markup and features are part of a specific html version (5.0, 5.1, etc.) or CSS or JavaScript release. Lock that down and move to the next version. Declare your supported version in the agent string instead of wanting a specific browser engine like Chrome. Relying on Chrome is like the Internet Explorer debacle all over again.

If the app doesn’t the render the declared version properly, then that’s on the app. If the dev uses out of spec or experimental features, that’s on the dev.

I’d much rather see an alert that says “This site requires HTML 5.0.1 or higher” than “This site doesn’t work in Firefox.”