4 ms·

It's nice to see WebKit adopt this approach too. Chrome and Firefox have already had a policy against new CSS properties with vendor prefixes for over three yea

It's nice to see WebKit adopt this approach too. Chrome and Firefox have already had a policy against new CSS properties with vendor prefixes for over three years, so with Safari onboard too now it's becoming easier to imagine a future where web developers won't have to worry about writing code with prefixes anymore. The only potential reason to use them will be compatibility with older browser versions.

aiiane 10y ago
Technically, web developers should never had to have worried about writing code with prefixes - prefixed properties were never intended to be used for production apps. :)
- sdegutis 10y ago
  The problem is that "production" can have varying levels of tolerance to cutting edge features depending on who the audience is. Sometimes you know all your people are Chrome users, or IE10 users, or developers with the latest browsers, etc.
  - digi_owl 10y ago
    And then it stays in production way way beyond the life time of your target audience, and we have ourself a IE6 situation all over again...
    - ry_ry 10y ago
      We do, it's the IE9 situation! I was looking at our browser metrics the other day and it's yet to drop below the arbitrary 5% usage figure we use to fully deprecate browser support. We are a public facing site, and not particularly niche. It's hovering around there, but if a user is still clinging to ie9 it's highly likely they don't have the ability or requirement to upgrade. When ie9 legacy support drops my biggest headache will be ie10's squiffy flexbox support.
      - eterm 10y ago
        IE9 is the highest available on Vista, and Vista is still in extended support until April 11, 2017. I'm planning a party for that date.
      - cptskippy 10y ago
        Having to support ie10 isn't the worst thing in the world. I was surprised when it was released because it was the first time I had ever marked up a page and it worked across all 4 browsers almost pixel perfect without any hacks or tweaks.
      - WorldMaker 10y ago
        You should only really need to worry about IE10 if you have users on Windows Server 2012 baseline, whom should have likely already upgraded to R2 or more recent. Lifecycle support jumps to 11 on most OSes, yay! https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-I...
        ry_ry 10y ago
        If only :( IE10 is a non-trivial portion of our desktop traffic, not to mention Trident's hateful mobile incarnation, which still turns up from time to time.
  - masklinn 10y ago
    The problem is not the tolerance to cutting edge, it's that the original point of prefixed properties was they were unstable and could be changed slightly or completely. Once you've shipped to production that's dead, there's no guarantee you'll update it.
- digi_owl 10y ago
  Yeah right. web devs (and sadly also other devs) are like magpies, always hunting for that latest shiny to add to their nest.
  - proksoup 10y ago
    Border radius with prefixes instead of with images felt elegant and simple and not shiny at the time (relative to what we were replacing).
    - jwdunne 10y ago
      Yeah. 4 - 5 lines of CSS far out strips 4 corner images and several extra divs, the typical implementation.
      - aplummer 10y ago
        Agreed, I would also say it's often not just the devs who build the requirements, hard to say something is impossible / not a good idea to implement when it's everywhere.
      - tehwebguy 10y ago
        And all those hours spent on A List Apart's "sliding door" tutorial for rounded corners
ryanSrich 10y ago
Should always use an auto-prefixer anyway, but your point is still valid.
kuschku 10y ago
And still Chrome requires us to use -webkit-animation even today.
- paulirish 10y ago
  Chrome hasn't required a prefix on animation since Chrome 43. (mid-2015)
herbst 10y ago
I was not even aware that safari is a exception here. I just did not use prefixes since about beginning 2015.

aiiane 10y ago

Technically, web developers should never had to have worried about writing code with prefixes - prefixed properties were never intended to be used for production apps. :)

sdegutis 10y ago
The problem is that "production" can have varying levels of tolerance to cutting edge features depending on who the audience is. Sometimes you know all your people are Chrome users, or IE10 users, or developers with the latest browsers, etc.
- digi_owl 10y ago
  And then it stays in production way way beyond the life time of your target audience, and we have ourself a IE6 situation all over again...
  - ry_ry 10y ago
    We do, it's the IE9 situation! I was looking at our browser metrics the other day and it's yet to drop below the arbitrary 5% usage figure we use to fully deprecate browser support. We are a public facing site, and not particularly niche. It's hovering around there, but if a user is still clinging to ie9 it's highly likely they don't have the ability or requirement to upgrade. When ie9 legacy support drops my biggest headache will be ie10's squiffy flexbox support.
    - eterm 10y ago
      IE9 is the highest available on Vista, and Vista is still in extended support until April 11, 2017. I'm planning a party for that date.
    - cptskippy 10y ago
      Having to support ie10 isn't the worst thing in the world. I was surprised when it was released because it was the first time I had ever marked up a page and it worked across all 4 browsers almost pixel perfect without any hacks or tweaks.
    - WorldMaker 10y ago
      You should only really need to worry about IE10 if you have users on Windows Server 2012 baseline, whom should have likely already upgraded to R2 or more recent. Lifecycle support jumps to 11 on most OSes, yay! https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-I...
      - ry_ry 10y ago
        If only :( IE10 is a non-trivial portion of our desktop traffic, not to mention Trident's hateful mobile incarnation, which still turns up from time to time.
- masklinn 10y ago
  The problem is not the tolerance to cutting edge, it's that the original point of prefixed properties was they were unstable and could be changed slightly or completely. Once you've shipped to production that's dead, there's no guarantee you'll update it.
digi_owl 10y ago
Yeah right. web devs (and sadly also other devs) are like magpies, always hunting for that latest shiny to add to their nest.
- proksoup 10y ago
  Border radius with prefixes instead of with images felt elegant and simple and not shiny at the time (relative to what we were replacing).
  - jwdunne 10y ago
    Yeah. 4 - 5 lines of CSS far out strips 4 corner images and several extra divs, the typical implementation.
    - aplummer 10y ago
      Agreed, I would also say it's often not just the devs who build the requirements, hard to say something is impossible / not a good idea to implement when it's everywhere.
    - tehwebguy 10y ago
      And all those hours spent on A List Apart's "sliding door" tutorial for rounded corners

ryanSrich 10y ago

Should always use an auto-prefixer anyway, but your point is still valid.

kuschku 10y ago

And still Chrome requires us to use -webkit-animation even today.

paulirish 10y ago
Chrome hasn't required a prefix on animation since Chrome 43. (mid-2015)

herbst 10y ago

I was not even aware that safari is a exception here. I just did not use prefixes since about beginning 2015.