Like to augment this concern? Update issue so it focuses primarily on one issue just by modifying this post.
Closed 7 in years past
Would individuals here send a niche site that shows a nice summary of which seller specific CSS3 extensions – e.g. -moz-border-radius – will still be needed or may be deprecated?
From everything I have seen generally all present variations of Chrome, Safari and Opera (disregard IE, i could stay without one for my personal recent application) are more often than not pleased to accept the W3C qualities without any seller prefixes.
6 Solutions 6
I will suggest utilizing the CanIUse website to test this.
The quick answer is that you need seller prefixes for exactly what previously utilized them — aided by the caveat so it is determined by what lengths straight back you wish to support older web browser versions.
The CanIUse webpages consists of browser help tables for nearly all internet browser ability imaginable, and almost any internet browser you’d wanna supporting. It includes records in which particular browsers support an element but need a vendor prefix.
You need to use these tables to determine yourself which prefixes are worth maintaining and that you’ll decrease.
Because you’ve requested specifically about border-radius , why don’t we look at the service desk for it: http://caniuse.com/#search=border-radius
This proves united states that no present browser adaptation calls for a prefix. But Firefox demanded the prefix to v3.6, Chrome up to 4.0, and Safari to 4.0. Portable Safari (3.2) and Android internet browser (2.1) additionally appear within the record.
If you need to help those browser forms or previous, then you will want the prefixes. Otherwise, you will get out with out them.
Hope that can help.
They likewise have it in book kind, the ebook of CSS3 by Peter Gasston, with which has tables noting all CSS3 browser service. Nonetheless we gamble thats the very last thing you wanted to find. and this maybe?
If prefixes are you’re interested in, the amazing http://shouldiprefix.com/ is probably what you are looking.
Great matter- i possibly couldn’t come across a worldwide research for vendor-prefix criteria.
Used to do an instant search on caniuse.com your vendor-prefixed homes i am making use of in my projects, and this refers to everything I receive (as of late 2013):
- border-radius: not necessary
- box-shadow: not needed
- box-sizing: -moz- necessary for current/future chrome
- transform: -webkit- necessary for all chrome/webkit browsers
- gradient: -webkit- necessary for recent android os browsers also recent
- linear-gradient: -webkit- necessary for current android os browsers along with other current box-sizing
- input-placeholder: not needed
- background-clip: not required
- user-select: necessary for all
(NOTE: we defined “not necessary” as not being necessary for any internet what is a sugar daddy browser with 1% + worldwide practices)
Please add to this.
PUBLIC-SERVICE ANNOUNCEMENT: understand that when working with vendor-prefixed properties, they should always arrive prior to non-vendor-prefixed attributes:
The nearest feasible to the full summary, try creating your personal selective overview with the large JS-Compatibility-Table, analyzing window.document.documentElement.style, the object used to detect support for some CSS Feature.
It’ll offer you a convenient dynamic dining table of most recognized W3C CSS attributes, by browser, utilizing the camelCased CSS keyword version, having the ability to find the browsers you’re concentrating on to compliment. The still within this concern are subject to change over opportunity.
The top JS-Compatibility-Table isn’t a rather are already aware of site produced by @TobiasBuschor, but dead handy. I personally use this dining table fairly often to check various homes or apis, or cross-check with caniuse information.
The W3C will not fully keep track of being compatible or what implementors do or launch. And browser designers themselves, aside from perhaps Opera, didn’t document these things really after all until more recently.
For identifying the choice about what browsers become sensible to deprecate support for (by removing owner prefix that will call for all of them). It will depend on confirmed site’s function demands.
The somewhat acknowledged meeting around this crafting is the fact that it really is okay to deprecate support for any web browser perhaps not promote querySelector , localStorage and addEventListener . Meaning you can properly drop support for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and every thing under.
That’s to state, it’s a little too very early right now to get rid of vendor prefixes, especially because millions of customers still incorporate Android os 2.x or 4.3 equipment, working Safari 4.x/5.x levels Android Stock Browsers, or Opera Mini (Presto 11). Those signify about 10% of global web browser practices in 2014.
In this class, border-radius is in fact the only person ability fairly safer to drop nowadays. Even though you could decided to drop rest, if you decide to help just the latest browsers. It might be at your own hazard and accountability of splitting compatibility with older browsers nevertheless heavily used.
It’s going to take quite some years still, one which just intentionally beginning shedding prefixes entirely.
