2 ms·
Yeah, but compatibility is already defined as "what chrome does". To be clear I mean quirks, not features. You can easily make objective comparisons on "does fe
by olliej 5y ago
Yeah, but compatibility is already defined as "what chrome does". To be clear I mean quirks, not features. You can easily make objective comparisons on "does feature exist in browser Y" so I'll leave that as an exercise for the reader :D
But "compatibility" is things like layout quirks, and before Chrome was the IE of the web, "correct behavior" was "what IE does". A lot of the IE escape was engineering effort devoted to developing IE compatibility. A chrome monopoly is going mean google has functionally complete control of the web, so they can simply state that their behavior is the spec. On top of that they already regularly force the addition of google identity based spying directly into the browser.
- mmis1000 5y agoIt 'is' already working in this way. Firefox do support a few WebKit prefixed api due to heavy usage by web developers (also because chrome never finalize them, let them keep prefixed) https://caniuse.com/css-line-clamp https://caniuse.com/css-line-clamp