3 ms·
I have to agree totally. This change is asinine. They're basically inserting a regression away from standards just so content will look slightly better in their
by djsumdog 10y ago
I have to agree totally. This change is asinine. They're basically inserting a regression away from standards just so content will look slightly better in their bowser (To gain browser share?)
- EdSharkey 10y agoI think Firefox will continue to support non-prefixed equivalents as well. Also, it seems like there are some useful -webkit- prefixed CSS properties that haven't yet been standardized with an unprefixed name. I think this is a good thing, they're adding new features that will (hopefully) get standardized someday. Let's heap some scorn on those websites and internal corporate teams that do all their work on Chrome and Safari and never test on other browsers. It's always laziness (not testing their crap at all) or lame excuses (Chrome is faster, why would I bother?) that's to blame. I don't mind being the "Firefox guy" on teams I'm part of and making sure my baby always gets some love.
- masklinn 10y agoThere's no regression from standard, they're not removing standard support.
- otabdeveloper1 10y ago> They're basically inserting a regression away from standards just so content will look slightly better in their browser The so-called 'standards' have been dead since Google forced to rubber-stamp the SPDY protocol as HTTP2. We're gonna have to learn to live in a world where the Internet is owned by Google.
- bzbarsky 10y agoThis stuff is being standardized. See https://compat.spec.whatwg.org/#css-properties https://compat.spec.whatwg.org/#css-properties