3 ms·

This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and

This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google's way or highway. EDIT: You can filter by features that both Firefox and Chrome support by tapping the Chrome icon. This takes the list from 63 entries to 29

notpushkin 2y ago
You can compare with Firefox by clicking on the Chrome icon – even enable both to see only features supported by both. (I think it would be a nice default view, though.)
- K0nserv 2y ago
  Thanks! I totally missed that
deleted 2y ago
[deleted]
ChrisArchitect 2y ago
Geez was staring at this trying to find icons and didn't realize on mobile the bottom drawer wasn't just part of the browser. Good stuff. Took this fun milk carton concept to a usable next level.
lucideer 2y ago
I think the feature to compare could be made a little more obvious - I can see why they would default to Chrome (both the most popular browser & also the one that shows the starkest difference), but tbh I find the most interesting comparison being against macOS Safari - that list seems really surprising to me. This also would of course be even nicer if you could define any browser as the "target" (e.g. compare Chrome -vs- Firefox) but then that wouldn't serve their very nice domain purchase as neatly.
- plufz 2y ago
  Yeah, I would like to know more about the Mac vs iOS WebKit as well. I would have guessed that the development of both would be done by the same team and that it would be very close for all features where they didn’t take a strategic decision to hinder web apps on the phone or performance/ux. But for example not having the autofocus attribute or pseudo selection css seems a little strange even though I can see how it could affect ux on the phone, especially the autofocus which would show the keyboard.
rainbowzootsuit 2y ago
I think it's normally "harebrained" like hare/rabbit but hair brain doesn't imply any greater intelligence for sure. I've said folks are "single threads" to indicate something similar in more nerdy settings.
- K0nserv 2y ago
  Right you are! I guess I'm one of today's 10000
pjmlp 2y ago
With the help of a generation of developers hating Microsoft and IE, Google has managed to turn the Web into ChromeOS.
deleted 2y ago
[deleted]

notpushkin 2y ago

You can compare with Firefox by clicking on the Chrome icon – even enable both to see only features supported by both. (I think it would be a nice default view, though.)

K0nserv 2y ago
Thanks! I totally missed that

deleted 2y ago

[deleted]

ChrisArchitect 2y ago

Geez was staring at this trying to find icons and didn't realize on mobile the bottom drawer wasn't just part of the browser. Good stuff. Took this fun milk carton concept to a usable next level.

lucideer 2y ago

I think the feature to compare could be made a little more obvious - I can see why they would default to Chrome (both the most popular browser & also the one that shows the starkest difference), but tbh I find the most interesting comparison being against macOS Safari - that list seems really surprising to me. This also would of course be even nicer if you could define any browser as the "target" (e.g. compare Chrome -vs- Firefox) but then that wouldn't serve their very nice domain purchase as neatly.

plufz 2y ago
Yeah, I would like to know more about the Mac vs iOS WebKit as well. I would have guessed that the development of both would be done by the same team and that it would be very close for all features where they didn’t take a strategic decision to hinder web apps on the phone or performance/ux. But for example not having the autofocus attribute or pseudo selection css seems a little strange even though I can see how it could affect ux on the phone, especially the autofocus which would show the keyboard.

rainbowzootsuit 2y ago

I think it's normally "harebrained" like hare/rabbit but hair brain doesn't imply any greater intelligence for sure. I've said folks are "single threads" to indicate something similar in more nerdy settings.

K0nserv 2y ago
Right you are! I guess I'm one of today's 10000

pjmlp 2y ago

With the help of a generation of developers hating Microsoft and IE, Google has managed to turn the Web into ChromeOS.

deleted 2y ago

[deleted]