Should fix this concern? Update issue as a result it centers on one problem best by editing this article.
Shut 7 years back
Would any person here post a site that presents a nice overview which merchant certain CSS3 extensions – e.g. -moz-border-radius – remain required or may be deprecated?
From everything I have seen by-and-large all present variations of Chrome, Safari and Opera (forget IE, I can stay without it for my personal recent app) tend to be in general happy to accept the W3C features without provider prefixes.
6 Responses 6
I will suggest making use of the CanIUse site to check this.
The brief response is that you have to have provider prefixes for whatever actually put them — because of the caveat so it is dependent upon what lengths back once again you want to supporting older web browser forms.
The CanIUse webpages contains browser help tables for nearly all browser ability imaginable, and almost any internet browser you’ll need supporting. It provides notes in which specific browsers help an attribute but require a vendor prefix.
You can make use of these dining tables to decide on your own which prefixes can be worth maintaining and that you’ll shed.
As you’ve expected specifically about border-radius , let’s check out the support dining table for it: http://caniuse.com/#search=border-radius
This indicates united states that no latest internet browser version requires a prefix. But Firefox demanded the prefix as much as v3.6, Chrome doing 4.0, and Safari to 4.0. Mobile Safari (3.2) and Android web browser (2.1) furthermore appear into the list.
If you need to help those browser versions or earlier, then you will want the prefixes. Or else, you can acquire aside without them.
Wish that helps.
They likewise have it in-book form, The Book of CSS3 by Peter Gasston, that contains dining tables listing all the CSS3 web browser support. Nonetheless I gamble thats the very last thing you wanted to take into consideration. so this perhaps?
If prefixes are common you’re interested in, the amazing http://shouldiprefix.com/ is probably what you are in search of.
Big question- i really couldn’t find a major international guide for vendor-prefix requisite.
I did so a simple browse caniuse.com your vendor-prefixed residential properties i am using inside my work, and this refers to everything I receive (recently 2013):
- border-radius: not necessary
- box-shadow: not needed
- box-sizing: -moz- required by current/future chrome
- change: -webkit- required by all chrome/webkit browsers
- gradient: -webkit- required by latest android browsers as well as other present
- linear-gradient: -webkit- necessary for current android os browsers alongside current box-sizing
- input-placeholder: not needed
- background-clip: not needed
- user-select: required by all
(NOTE: we described “not needed” as not required by any internet browser with 1% + worldwide practices)
Feel free to add to this.
PUBLIC-SERVICE STATEMENT: understand that when making use of vendor-prefixed homes, they need to constantly arrive prior to non-vendor-prefixed attributes:
The closest possible to a full overview, was creating your own selective overview utilising the larger JS-Compatibility-Table, taking a look at window.document.documentElement.style, the item used to identify support for a particular CSS function.
It is going to present a convenient powerful dining table of all backed W3C CSS residential properties, by browser, by using the camelCased CSS keyword version, having the ability to find the browsers you might be targeting to compliment. The however contained in this matter are subject to change over time.
The top JS-Compatibility-Table is not a really well know site created by @TobiasBuschor, but dead handy. I use this table most of the time to test different properties or apis, or cross-check with caniuse facts.
The W3C doesn’t completely monitor being compatible or just what implementors actually do or launch. And browser producers themselves, except for possibly Opera, didn’t record this stuff really at all until more recently.
For determining the decision in regards to what browsers include sensible to deprecate assistance for (by detatching the seller prefix which will need all of them). It’s going to be determined by confirmed website’s feature requirement.
The somewhat recognized convention around this authorship would be that it is alright to deprecate support for just about any internet browser perhaps not promote querySelector , localStorage and addEventListener . Meaning it is possible to properly drop assistance for Firefox 3.5, IE 8, Safari 3.2, Chrome 3 escort services in Long Beach, Opera Presto 10.1 and every thing under.
That’s to state, its a touch too early at this time to get rid of supplier prefixes, especially simply because countless people nonetheless use Android os 2.x or 4.3 systems, run Safari 4.x/5.x values Android inventory Browsers, or Opera Mini (Presto 11). Those portray about 10% of global web browser consumption in 2014.
In this group, border-radius is in fact the only person function pretty safe to decrease now. As you could decided to fall rest, if you choose to supporting precisely the latest browsers. It might be at your very own chances and accountability of busting compatibility with old browsers however seriously utilized.
It takes quite some years however, before you could intentionally start falling prefixes totally.