4 ms·
I think Firefox will continue to support non-prefixed equivalents as well. Also, it seems like there are some useful -webkit- prefixed CSS properties that have
by EdSharkey 10y ago
I 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.