Browsers situationship: When browsers agree but the spec doesn't

Browsers situationship: When browsers agree but the spec doesn't atbrakhi.dev

What came first: browsers or specifications? Why are specifications important? Why do we sometimes change a specification instead of browsers? What matters most: the specification or the user experience? What happens…

14 points•cpeterso•7 days ago•6 comments•

#browsers #agree #spec #situationship #browsers situationship #browsers agree #specifications #came

6 comments

hollow-moe5 days ago

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.

rrr_oh_man5 days ago

It's like the UN, basically

lukan5 days ago

It is like power works since probably forever.

adzm5 days ago

Are there any more examples other than the newlines thing?

throwaway6462335 days ago

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.

lukebitts5 days ago

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

Read the full thread on Hacker News →

6 comments

Related stories