alt Hacker NewsThere’s quite a few edge cases where browsers allow non-compliant code to render as if it were to specs. Because if a site doesn’t render “correctly” from a user perspective, they blame the browser rather than blaming the web developer.
There’s quite a few edge cases where browsers allow non-compliant code to render as if it were to specs. Because if a site doesn’t render “correctly” from a user perspective, they blame the browser rather than blaming the web developer.
That does happen, but these days they tend to add that kind of thing to the spec (and the test suite). There was a minor drama several years when WHATWG (representing browser vendors) effectively took over the spec process from the W3C because they were fed up with the W3C taking an idealistic viewpoint, and speccing things that they couldn't actually implement.