Browsers situationship: When browsers agree but the spec doesn't
atbrakhi.dev
2 threads
Spec says Y, Chrome does X, all its forks do X, web devs expect X, Firefox, Safari etc. must implement X, spec is rewritten to say X. It's as simple as that.
It's like the UN, basically
It is like power works since probably forever.
Are there any more examples other than the newlines thing?
I worked on Internet Explorer implementing part of the SVG spec. There was one case where the spec said one thing and the other browser vendors did something different, so I got buy-in to declare the spec as incorrect and matched the prevailing behavior.
The only reason I clicked on the link was to read a list of examples, but for some reason the author seems to really want to define what a situationship is instead, disappointing