> I don't remember Netscape/Mozilla/Firefox ever changing their behaviour to match a standard, they just got their behaviour declared as the standard and ignore

> I don't remember Netscape/Mozilla/Firefox ever changing their behaviour to match a standard, they just got their behaviour declared as the standard and ignored the cases where they didn't. This is not even remotely true. There’s thousands upon thousands of bugs publicly available in Bugzilla showing fixes to standards conformance, not to mention the Acid Test and things like that. As far as “got their behaviour declared as the standard”, in several important cases the opposite is true. The reason why Netscape 4 was so terrible with CSS is because there were two competing approaches for styling – CSS, which Microsoft had already started implementing; and JSSS which Netscape had already started implementing. The W3C picked CSS, and Netscape scrambled to catch up by transcoding CSS into JSSS as a stopgap measure. Which is also why Netscape 4 lost CSS support when JavaScript was disabled.