Could there be a browser-compatibility deprecation desk for CSS3 seller prefixes? [closed]

Could there be a browser-compatibility deprecation desk for CSS3 seller prefixes? [closed]

Like to fix this concern? Update practical question as a result it centers on one difficulty merely by modifying this blog post.

Shut 7 years back

daniel levy dating

Would any person here send a website that presents a cool overview which merchant specific CSS3 extensions — e.g. -moz-border-radius — will still be requisite or is generally deprecated?

From everything I have experienced more often than not all latest forms of Chrome, Safari and Opera (disregard IE, I’m able to stay without it for my current application) become by-and-large happy to live with the W3C qualities without provider prefixes.

6 Responses 6

I suggest by using the CanIUse webpages to test this.

The quick answer is that you’ll require provider prefixes for everything that actually ever used them — using caveat that it is dependent upon how far right back you should support old internet browser forms.

The CanIUse web site has browser support dining tables for just about any internet browser ability you can imagine, and pretty much every browser you might wanna supporting. It includes records where particular browsers support an element but need a vendor prefix.

You can make use of these tables to decide for your self which prefixes are worth maintaining and which you’ll decrease.

As you’ve expected especially about border-radius , why don’t we go through the assistance dining table for this:

This proves you that no recent web browser version need a prefix. But Firefox demanded the prefix doing v3.6, Chrome around 4.0, and Safari doing 4.0. Cellular phone Safari (3.2) and Android os Browser (2.1) furthermore appear into the number.

If you want to supporting those browser variations or previous, then you need the prefixes. Normally, you can acquire away with out them.

Expect that helps.

They likewise have they in-book type, the ebook of CSS3 by Peter Gasston, which has dining tables listing the CSS3 browser assistance. However I wager thats the very last thing you wanted to think about. which means this possibly?

If prefixes are common you find attractive, the awesome is most likely what you’re wanting.

Fantastic concern- i possibly couldn’t come across a global reference for vendor-prefix requirements.

I did so an instant explore your vendor-prefixed residential properties i am utilizing in my projects, and this is the things I discover (recently 2013):

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

(NOTE: I identified «not essential» as not-being necessary for any internet browser with 1percent + worldwide usage)

Go ahead and increase this.

PUBLIC-SERVICE STATEMENT: Remember that when working with vendor-prefixed homes, they need to usually appear before non-vendor-prefixed residential properties:

The closest feasible to the full overview, is generating your selective overview by using the larger JS-Compatibility-Table, analyzing, the object which is used to detect support for some CSS Feature.

It will probably supply a convenient powerful desk of all of the recognized W3C CSS properties, by web browser, with the camelCased CSS keyword version, have real profit select the browsers you happen to be concentrating on to guide. The nonetheless contained in this matter are at the mercy of change over time.

The major JS-Compatibility-Table isn’t a very are already aware of site created by @TobiasBuschor, but dead handy. I personally use this table fairly often to check on different homes or apis, or cross-check with caniuse information.

The W3C cannot totally keep track of being compatible or just what implementors actually do or release. And browser manufacturers themselves, except for possibly Opera, didn’t record these things well whatsoever until now.

For deciding the selection in regards to what browsers become reasonable to deprecate service for (by removing the seller prefix that would need all of them). It will be determined by certain web site’s function requirements.

The quite accepted convention around this crafting would be that it’s ok to deprecate support regarding browser perhaps not supporting querySelector , localStorage and addEventListener . Meaning you can safely decrease support for Firefox 3.5, IE 8, Safari 3.2, Chrome 3, Opera Presto 10.1 and anything underneath.

Basically to express, it really is a little too very early at this time to take out supplier prefixes, particularly because of the fact countless consumers nonetheless incorporate Android os 2.x or 4.3 tools, run Safari 4.x/5.x degree Android Stock Browsers, or Opera Mini (Presto 11). Those portray about 10percent of international browser practices in 2014.

In that category, border-radius is in fact alone element rather safer to decrease nowadays. Whilst you could made a decision to drop others, if you choose to supporting only the latest browsers. It will be at your very own chances and responsibility of splitting compatibility with old browsers nevertheless greatly used.

It takes quite a few years however, before you can intentionally start losing prefixes totally.