4 ms·
Could you share the specifics of your example with the Chrome team refusing to implement already existing standards?
by rmdashrfstar 7y ago
Could you share the specifics of your example with the Chrome team refusing to implement already existing standards?
- bzbarsky 7y agoThe discussion in https://github.com/heycam/webidl/pull/357 https://github.com/heycam/webidl/pull/357 is one example (the Web IDL spec defined the behavior of all the non-Chrome browsers as the spec behavior, then Chrome introduced a third behavior that they want to implement and is trying to get the spec changed to match it). There were several things in the flexbox spec where Chrome refused to implement what everyone else was doing and the spec ended up getting changed, but I don't have links offhand, sorry. It would take me some hours of digging through bug reports and mailing lists to find them. In general, there have been a lot of things like this in the CSS world that I see peripherally, but I'm not as involved in that personally, so don't have them at the tips of my fingers. A recent thing that came up is that the behavior of the `disabled` property on `HTMLLinkElement` in Chrome does not match the (very long-standing; literally decades) spec, and it looks like at this point we're going to need to change the spec to match Chrome because sites are writing code to the Chrome implementation, not to the spec, and it's causing compat problems for Firefox (which does implement the spec). Now don't get me wrong: there are lots of cases in which Chrome _does_ fix longstanding spec-compliance issues. But that's not the only dynamic happening here.