Firefox

4071 readers

1 users here now

A community for discussion about Mozilla Firefox.

founded 1 year ago

MODERATORS

[email protected]

180

In an alternate timeline... (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

A Mozilla employee recently released a Firefox addon to change the user agent to Chrome on sites the user enables it on.

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

[–] [email protected] 72 points 2 months ago* (last edited 2 months ago) (3 children)

You shouldn’t have to do this. I blame W3C org and their ilk for putting the rendering engine, browser brand, and browser version in the response header. All your browser should be telling the site is the versions of html, css, and JavaScript it supports and whether it’s mobile or desktop.

[–] [email protected] 21 points 2 months ago

Your ideas are intriguing to me and I wish to subscribe to your newsletter.

[–] [email protected] 13 points 2 months ago

versions of html, css, and JavaScript it supports

Given the level of support a browser has for something is basically the browser's version (there's no such thing as a version number for JavaScript or CSS for example, there's a spec that's kinda versioned, but browsers don't implement everything the same), you've basically just described user agent strings

We have feature detection approaches today that make UA based browser detection generally unnecessary but the horse has already bolted on that now

[–] [email protected] 6 points 2 months ago

The evolution of the user-agent string isn't exactly the W3C's fault.

https://webaim.org/blog/user-agent-string-history/