Wanna improve this question? Update practical question so that it targets one problem merely by editing this blog post.
Shut 7 years back
Would people here posting a site that shows a neat overview which merchant specific CSS3 extensions – e.g. -moz-border-radius – are still requisite or is generally deprecated?
From the thing I have experienced generally all current versions of Chrome, Safari and Opera (skip IE, i will reside without one for my personal recent software) is in general thrilled to live with the W3C features without any vendor prefixes.
6 Responses 6
I will suggest utilising the CanIUse site to evaluate this.
The quick response is that you’ll require merchant prefixes for everything that ever before utilized all of them — aided by the caveat that it hinges on how long right back you intend to support outdated browser versions.
The CanIUse website consists of browser service tables for virtually every web browser ability you can imagine, and almost every internet browser you would desire to supporting. It provides notes where certain browsers support an element but call for a vendor prefix.
You can utilize these dining tables to determine for your self which prefixes can be worth keeping and which you are able to drop.
Due to the fact’ve expected specifically about border-radius , let’s go through the service table for this: http://caniuse.com/#search=border-radius
This shows united states that no latest internet browser variation need a prefix. But Firefox demanded the prefix around v3.6, Chrome doing 4.0, and Safari doing 4.0. Smartphone Safari (3.2) and Android os Browser (2.1) also arrive within the listing.
If you want to supporting those browser versions or earlier, then you will want the prefixes. Usually, you could get aside with out them.
Hope that assists.
They likewise have they in-book type, the ebook of CSS3 by Peter Gasston, that has had tables detailing the CSS3 internet browser support. Nevertheless we staked thats the last thing you desired to take into account. and this perhaps?
If prefixes are common you’re interested in, the awesome http://shouldiprefix.com/ might be what you’re searching for.
Great concern- I couldn’t get a hold of a major international research for vendor-prefix requisite.
I did so a quick search on https://datingmentor.org/escort/los-angeles/ caniuse.com when it comes down to vendor-prefixed residential properties i am utilizing during my work, and this refers to the thing I receive (as of late 2013):
- border-radius: not necessary
- box-shadow: not necessary
- box-sizing: -moz- required by current/future chrome
- modify: -webkit- necessary for all chrome/webkit browsers
- gradient: -webkit- necessary for existing android os browsers as well as other current
- linear-gradient: -webkit- required by current android os browsers as well as other previous box-sizing
- input-placeholder: not essential
- background-clip: not necessary
- user-select: necessary for all
(NOTICE: I described “not required” as not-being necessary for any browser with 1per cent + global use)
Go ahead and enhance this.
PUBLIC SERVICE ANNOUNCEMENT: keep in mind that when using vendor-prefixed properties, they should usually appear prior to non-vendor-prefixed properties:
The closest feasible to a full summary, try producing your own personal selective summary utilising the huge JS-Compatibility-Table, examining window.document.documentElement.style, the object which is used to identify help for a particular CSS function.
It’s going to provide you with a convenient vibrant dining table of all recognized W3C CSS properties, by browser, utilizing the camelCased CSS key phrase version, with the ability to find the browsers you will be targeting to guide. The nonetheless within concern becoming subject to change over opportunity.
The major JS-Compatibility-Table isn’t a rather well know source from @TobiasBuschor, but very handy. I personally use this desk fairly often to check different attributes or apis, or cross-check with caniuse data.
The W3C doesn’t totally track compatibility or exactly what implementors actually do or release. And browser designers on their own, excepting probably Opera, failed to report these items well anyway until now.
For identifying the choice about what browsers are sensible to deprecate assistance for (by detatching the seller prefix which may need all of them). It is going to be determined by certain web site’s element requirements.
The somewhat acknowledged convention as of this crafting is that it’s alright to deprecate help for web browser not supporting querySelector , localStorage and addEventListener . Meaning you can easily safely decrease help for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and everything underneath.
In fact it is to say, its a little too very early nowadays to remove provider prefixes, especially because of the fact many users still use Android os 2.x or 4.3 systems, operating Safari 4.x/5.x stages Android os Stock Browsers, or Opera Mini (Presto 11). Those represent about 10percent of global web browser practices in 2014.
In that category, border-radius is pretty much alone ability pretty secure to decrease nowadays. Even though you could decided to fall rest, if you choose to support just the latest browsers. It would be at the own chances and accountability of breaking compatibility with older browsers nonetheless seriously made use of.
It’s going to take many years still, before you could intentionally beginning shedding prefixes entirely.