Wish develop this concern? Update practical question therefore it focuses on one issue merely by editing this post.
Sealed 7 years back
Would anybody here post a website that shows a cool overview which supplier specific CSS3 extensions – e.g. -moz-border-radius – will still be called for or is deprecated?
From what I have experienced generally all previous models of Chrome, Safari and Opera (forget IE, I am able to live without one for my existing application) become more often than not happy to accept the W3C qualities without provider prefixes.
6 Solutions 6
I would suggest making use of the CanIUse site to check this.
The brief answer is that you have to have provider prefixes for whatever previously made use of all of them — utilizing the caveat which will depend on what lengths straight back you want to help old internet browser forms.
The CanIUse web site includes browser service dining tables for virtually every internet browser ability imaginable, and almost every web browser you might wish help. It offers notes where certain browsers help a feature but require a vendor prefix.
You need to use these tables to choose yourself which prefixes are worth keeping and which you are able to fall.
Since you’ve asked specifically about border-radius , why don’t we consider the support table for this: http://caniuse.com/#search=border-radius
This shows all of us that no recent internet browser type requires a prefix. But Firefox required the prefix up to v3.6, Chrome up to 4.0, and Safari to 4.0. Cellular phone Safari (3.2) and Android os web browser (2.1) furthermore show up when you look at the record.
If you wish to support those browser variations or earlier in the day, then you need the prefixes. If not, you will get away with https://datingmentor.org/canada-interracial-dating/ out them.
Wish that helps.
They also have they in-book type, The Book of CSS3 by Peter Gasston, which has had tables detailing every CSS3 web browser support. However we gamble thats the very last thing you wanted to consider. and this perhaps?
If prefixes are you’re interested in, the awesome http://shouldiprefix.com/ is probably what you are finding.
Fantastic concern- I couldn’t get a hold of an international research for vendor-prefix specifications.
I did so a quick browse caniuse.com for any vendor-prefixed properties I’m making use of inside my work, referring to what I receive (lately 2013):
- border-radius: not necessary
- box-shadow: not required
- box-sizing: -moz- required by current/future chrome
- modify: -webkit- required by all chrome/webkit browsers
- gradient: -webkit- necessary for existing android os browsers and various other recent
- linear-gradient: -webkit- required by present android browsers alongside recent box-sizing
- input-placeholder: not essential
- background-clip: not needed
- user-select: necessary for all
(NOTE: we explained “not essential” as not-being necessary for any internet browser with 1% + global use)
Go ahead and enhance this.
PUBLIC SERVICE ANNOUNCEMENT: understand that when utilizing vendor-prefixed land, they should always come before non-vendor-prefixed characteristics:
The closest feasible to the full overview, are producing your own selective overview with the huge JS-Compatibility-Table, looking at window.document.documentElement.style, the thing used to discover service for some CSS function.
It will probably provide you with a convenient vibrant table of backed W3C CSS land, by browser, utilising the camelCased CSS keywords variation, have real profit select the browsers you will be focusing on to aid. The nonetheless in this matter are subject to change-over opportunity.
The major JS-Compatibility-Table just isn’t a very well know reference made by @TobiasBuschor, but very handy. I take advantage of this table frequently to evaluate various properties or apis, or cross-check with caniuse facts.
The W3C does not completely track compatibility or exactly what implementors actually do or release. And browser manufacturers by themselves, with the exception of probably Opera, failed to document this stuff well anyway until now.
For identifying the selection about what browsers become sensible to deprecate help for (by detatching the seller prefix that will call for them). It is going to rely on a given website’s function criteria.
The somewhat approved meeting around this crafting would be that it’s okay to deprecate support for browser maybe not promote querySelector , localStorage and addEventListener . Meaning possible properly drop assistance for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and anything under.
Which is to say, it really is a little too very early at this time to eliminate seller prefixes, especially because millions of users still use Android os 2.x or 4.3 gadgets, operating Safari 4.x/5.x degrees Android Stock Browsers, or Opera Mini (Presto 11). Those represent about 10per cent of global browser consumption in 2014.
For the reason that classification, border-radius is in fact the only person element quite safer to drop now. As you could made a decision to decrease people, if you choose to support only the newest browsers. It could be at your own possibility and liability of splitting compatibility with old browsers nevertheless highly made use of.
It does take quite a few years still, before you could deliberately starting dropping prefixes entirely.
Comentários