Can there be a browser-compatibility deprecation dining table for CSS3 seller prefixes? [closed]

Want to augment this concern? Update the question so it concentrates on one complications best by editing this article.

Sealed 7 in years past

Would anybody right here publish a niche site that presents a neat summary that merchant certain CSS3 extensions — e.g. -moz-border-radius — continue to be required or are deprecated?

From what I have seen generally all present forms of Chrome, Safari and Opera (forget about IE, I am able to reside without it for my personal latest application) become more often than not very happy to live with the W3C characteristics with no merchant prefixes.

6 Responses 6

I would suggest making use of the CanIUse web site to test this.

The short response is that you might want vendor prefixes for whatever previously utilized all of them — using caveat it hinges on how far right back you intend to supporting old internet browser forms.

The CanIUse webpages contains browser service tables for just about any web browser element imaginable, and almost any web browser you might wanna support. It offers records in which certain browsers help a characteristic but call for a vendor prefix.

You can utilize these tables to decide for your self which prefixes are worth keeping and which you are able to fall.

As you’ve requested particularly about border-radius , let us glance at the support dining table for it: http://caniuse.com/#search=border-radius

This proves you that no current browser adaptation need a prefix. But Firefox recommended the prefix to v3.6, Chrome up to 4.0, and Safari doing 4.0. Mobile phone Safari (3.2) and Android web browser (2.1) in addition show up for the number.

If you would like support those browser forms or earlier in the day, then you need the prefixes. Otherwise, you can get out without them.

Wish that can help.

They also have it in-book type, the ebook of CSS3 by Peter Gasston, containing tables noting every CSS3 internet browser assistance. Nonetheless we guess thats the very last thing you wanted to look for. so this perhaps?

If prefixes are typical you have in mind, the amazing http://shouldiprefix.com/ might be what you are looking for.

Great question- i possibly couldn’t get a hold of a global resource for vendor-prefix requirements.

Used to do an instant explore caniuse.com when it comes down to vendor-prefixed qualities I’m making use of during my work, and this refers to everything I discovered (as of late 2013):

• border-radius: not required
• box-shadow: not needed
• box-sizing: -moz- required by current/future chrome
• change: -webkit- required by all chrome/webkit browsers
• gradient: -webkit- necessary for existing android os browsers also present
• linear-gradient: -webkit- required by existing android os browsers also previous box-sizing
• input-placeholder: not necessary
• background-clip: not required
• user-select: required by all

(MENTION: I described «not needed» as not being necessary for any internet browser with 1per cent + international consumption)

Go ahead and enhance this.

PUBLIC SERVICE ANNOUNCEMENT: keep in mind that whenever using vendor-prefixed homes, they should constantly are available prior to non-vendor-prefixed qualities:

The closest possible to the full overview, try creating yours discerning summary with the Big JS-Compatibility-Table, taking a look at window.document.documentElement.style, the thing which is used to recognize assistance for some CSS element.

It is going to give you a convenient dynamic dining table of supported W3C CSS land, by internet browser, using the camelCased CSS keyword version, with the ability to select the browsers you will be focusing on to aid. The however in this question becoming subject to change over energy.

The Big JS-Compatibility-Table is certainly not a very are already aware of source produced by @TobiasBuschor, but dead handy. I prefer this dining table frequently to check various characteristics or apis, or cross-check with caniuse facts.

The W3C does not fully monitor compatibility or just what implementors really do or release. And browser makers by themselves, excepting possibly Opera, don’t document this stuff really whatsoever until now.

For determining the decision in regards to what browsers tend to be affordable to deprecate support for (by detatching owner prefix which will require them). It is going to be determined by a given website’s ability requisite.

The somewhat acknowledged meeting as of this authorship is it is alright to deprecate assistance for any browser maybe not supporting querySelector , localStorage and addEventListener . Meaning possible safely fall assistance for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and anything below.

Which is to express, it’s a little too early right now to get rid of merchant prefixes, specifically because an incredible number of customers nevertheless use Android os 2.x or 4.3 tools, working Safari 4.x/5.x values Android inventory Browsers, or Opera Mini (Presto 11). Those represent about 10% of international web browser practices in 2014.

For the reason that group, border-radius is pretty much the only one feature fairly safe to drop nowadays. Although you could chose to decrease other individuals, if you opt to support precisely the latest browsers. It will be at your very own hazard and accountability of splitting being compatible with outdated browsers still greatly used.

It’s going to take quite some years nevertheless, before you can purposely start losing prefixes completely.