3 ms·
FWIW, that's a pretty standard behavior for Chrome teams) and, as far as I understand, related to how they are evaluated within Google. More spec proposals ==
by Yoric 4y ago
FWIW, that's a pretty standard behavior for Chrome teams) and, as far as I understand, related to how they are evaluated within Google.
More spec proposals == good for your career.
Shipping a feature (even if it's non-standard) == good for your career.
Ensuring standard-compatibility == noop.
Source: I used to be a browser dev annoyed by how Chrome kept shipping non-standard features.
- sam_goody 4y agoThat's a feature, not a bug. As long as Chrome has > 80% market share, the more non-standard features the ship, the more they cement their position. Same as IE6, which was intentionally non-standards. Sites would be designed to work in IE, and would not work on Netscape. Considering how much spying and how much lock-in Chrome provides for Google, anything that makes devs design for Chrome only is a huge advantage.