1 mo. ago • 98%

In an alternate timeline...

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

Firefox @lemmy.ml In an alternate timeline...

16 comments

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.

72
- Your ideas are intriguing to me and I wish to subscribe to your newsletter.
  
  21
- 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
  
  13
- The evolution of the user-agent string isn't exactly the W3C's fault.
  
  https://webaim.org/blog/user-agent-string-history/
  
  6
If only web standards were a thing

43
- If anything we have too many web standards.
  
  14
  
  Someone should really make a unifying standard.
  
  23
Hmm had no idea this existed, thanks for sharing

4
I believe the screenshot has a typo lol. The mask would be off if Firefox looks like Firefox.

2
- the screenshot shows them installing it on chrome, somehow. It doesn’t seem to exist for chrome. But if it did, off would be chrome and on would be firefox, which is what’s shown
  
  5
  
  So the mask is on in the screenshot? Like, a mask on the mask? This is so meta wtf
  
  2
Like a dusty Internet Explorer mask.

2

You've viewed 16 comments.