We have web standards, but one area they breakdown is adoption of those standards.
Each browser seems to pick and choose which standards they want to adopt and when. Sometimes Chrome will support a new CSS syntax for months or years before another browser finally picks up support (or vice versa).
For web standards to truly work, there would need to be better coordination between browsers to adopt new standards in unison. Until then, developers (should) keep track of whether the syntax they're using is supported by all major browsers. Or, develop just for Chrome, which seems to be favored by most.
We vendors disagree about the relative value of different standards. Adopting at different times makes life harder on web devs, but it also seems like the only route forward. Do you want any one vendor to be able to force the others to implement something they disagree with, or (vice versa) to have veto power?
Each browser seems to pick and choose which standards they want to adopt and when. Sometimes Chrome will support a new CSS syntax for months or years before another browser finally picks up support (or vice versa).
For web standards to truly work, there would need to be better coordination between browsers to adopt new standards in unison. Until then, developers (should) keep track of whether the syntax they're using is supported by all major browsers. Or, develop just for Chrome, which seems to be favored by most.