Desire to develop this question? Update the question so that it centers on one problem best by modifying this article.
Shut 7 in years past
Would individuals here post a website that displays a neat overview of which seller certain CSS3 extensions – e.g. -moz-border-radius – will always be required or could be christian chat room lebanese deprecated?
From the things I have seen by and large all present versions of Chrome, Safari and Opera (forget about IE, I can live without it for my recent software) were in general happy to live with the W3C characteristics without any vendor prefixes.
6 Answers 6
I would suggest by using the CanIUse webpages to evaluate this.
The quick response is that you’ll require vendor prefixes for precisely what ever before made use of them — with all the caveat that it will depend on what lengths back you want to supporting old web browser forms.
The CanIUse webpages has browser support dining tables for virtually every web browser element imaginable, and almost any web browser might need supporting. It includes notes where particular browsers support a characteristic but call for a vendor prefix.
You can utilize these dining tables to determine on your own which prefixes can be worth keeping and which you’ll shed.
As you’ve questioned especially about border-radius , why don’t we glance at the support desk for this: http://caniuse.com/#search=border-radius
This proves you that no latest internet browser variation requires a prefix. But Firefox necessary the prefix up to v3.6, Chrome around 4.0, and Safari as much as 4.0. Smartphone Safari (3.2) and Android os Browser (2.1) in addition arrive inside listing.
If you wish to support those browser versions or earlier in the day, you will need the prefixes. If not, you could get away without them.
Hope that can help.
They likewise have it in book kind, the ebook of CSS3 by Peter Gasston, that contains dining tables listing the CSS3 browser help. Nevertheless I guess thats the worst thing you wanted to think about. which means this possibly?
If prefixes are common you are interested in, the amazing http://shouldiprefix.com/ is most likely what you’re finding.
Big matter- i really couldn’t discover a global research for vendor-prefix demands.
I did a fast explore caniuse.com for any vendor-prefixed homes I’m utilizing during my projects, and this refers to the thing I found (lately 2013):
- border-radius: not needed
- box-shadow: not necessary
- box-sizing: -moz- required by current/future chrome
- modify: -webkit- required by all chrome/webkit browsers
- gradient: -webkit- required by present android os browsers along with other current
- linear-gradient: -webkit- necessary for present android os browsers along with other recent box-sizing
- input-placeholder: not necessary
- background-clip: not required
- user-select: required by all
(NOTICE: we identified “not essential” as not-being required by any web browser with 1% + international practices)
Feel free to increase this.
PUBLIC SERVICE STATEMENT: understand that whenever using vendor-prefixed properties, they ought to usually come prior to non-vendor-prefixed residential properties:
The closest feasible to the full overview, try making yours discerning summary using the large JS-Compatibility-Table, viewing window.document.documentElement.style, the item used to identify help for a specific CSS function.
It’ll provide you with a convenient powerful desk of most recognized W3C CSS qualities, by web browser, utilising the camelCased CSS keyword version, having the ability to find the browsers you might be focusing on to guide. The however contained in this matter being susceptible to change over energy.
The major JS-Compatibility-Table isn’t a tremendously well know resource from @TobiasBuschor, but dead handy. I use this desk fairly often to check different attributes or apis, or cross-check with caniuse information.
The W3C doesn’t fully monitor being compatible or what implementors actually do or release. And browser manufacturers on their own, with the exception of probably Opera, don’t document this stuff really after all until more recently.
For identifying the choice in regards to what browsers become reasonable to deprecate service for (by eliminating the vendor prefix which will call for them). It is going to rely on certain website’s ability requirement.
The quite approved convention around this authorship is that it really is all right to deprecate assistance for almost any browser not promoting querySelector , localStorage and addEventListener . Meaning possible safely decrease service for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and everything underneath.
That will be to state, it is a tad too very early at this time to eliminate seller prefixes, especially simply because countless consumers however need Android 2.x or 4.3 devices, running Safari 4.x/5.x grade Android os Stock Browsers, or Opera Mini (Presto 11). Those portray about 10% of global web browser use in 2014.
In this classification, border-radius is in fact the only one ability quite safer to decrease nowadays. Even though you could chose to shed other people, if you choose to help precisely the current browsers. It will be at the own hazard and liability of busting compatibility with outdated browsers still seriously used.
It does take many years nevertheless, one which just purposely start dropping prefixes entirely.