|Summary:||Unprefix CSS3 transitions, animations, and transforms|
|Severity:||Normal||CC:||7raivis, alexander.shalamov, andrew, boyerchen, bruno.abinader, chazeah, cowwoc, dino, dtrebbien, eoconnor, jussi.kukkonen, kenneth, laszlo.gombos, menard, m.goleb+bugzilla, mikelawther, paulirish, priyajeet.hora, simon.fraser, syoichi, webkit.bugzilla, yael|
|Version:||528+ (Nightly build)|
|Bug Depends on:||26770, 71584, 104802, 104803, 104805, 105036, 105446, 108809, 108810, 108811, 113648, 65793, 84426, 104804, 105035, 105426, 105428, 105430, 105432, 105442, 105647, 106245, 106369, 107134, 107319, 107986, 108216, 108751, 110011, 110074, 111201|
Description Eric 2012-08-03 10:18:46 PDT
Both FF (16) and Opera (12.5) have recently unprefixed transitions, animations, and transforms http://my.opera.com/ODIN/blog/2012/08/03/a-hot-opera-12-50-summer-time-snapshot https://hacks.mozilla.org/2012/07/aurora-16-is-out/
Comment 1 Jussi Kukkonen (jku) 2012-08-22 04:53:40 PDT
I could give this a go if you're not doing it. These -webkit-properties are in at least safari development docs so I assume there's pressure to keep the prefixed versions working as well?
Comment 2 Jussi Kukkonen (jku) 2012-08-22 05:19:24 PDT
*** Bug 94075 has been marked as a duplicate of this bug. ***
Comment 3 Simon Fraser (smfr) 2012-08-22 10:08:47 PDT
We need to make a bunch of behavior changes before we can drop prefixes on transforms. From memory: 1. Require units on perpective (function and property) 2. Implement transform function matching for animation according to the spec 3. Implement the 3D rendering context stuff properly (layer intersection) 4. Change background-attachment:fixed behavior. 5. Probably more. We'd want the prefixed properties to retain the current behavior.
Comment 4 Jussi Kukkonen (jku) 2012-08-23 00:21:42 PDT
(In reply to comment #3) > We need to make a bunch of behavior changes before we can drop prefixes on transforms. From memory: > 1. Require units on perpective (function and property) > 2. Implement transform function matching for animation according to the spec > 3. Implement the 3D rendering context stuff properly (layer intersection) > 4. Change background-attachment:fixed behavior. > 5. Probably more. Yeah, I figured I should have made this into three different bugs for the three areas before even asking... I'm mostly looking at Animation at this point, and so far haven't noticed anything crucial to be missing. I guess I should write to webkit-dev before wasting too much effort though. > We'd want the prefixed properties to retain the current behavior. Good to know, thanks.
Comment 5 Binyamin 2012-11-08 04:31:03 PST
> https://twitter.com/csswg/status/210404244682055680 6 Jun 2012 > CSS WG formally allows browser vendors to unprefix CSS 3 Transforms, Transitions, Animations ^DG
Comment 6 cowwoc 2014-11-05 13:11:25 PST
According to http://caniuse.com/#feat=css-animation the upcoming version of Chrome (39) will unprefix CSS animations. Opera will follow suit. This means the last browser not support unprefixed CSS animations will be webkit. Android Browser and Chrome for Android will follow suit 2-3 months later (they are 2 versions behind the desktop version).
Comment 7 Michał Gołębiowski-Owczarek 2016-01-26 01:36:42 PST
Isn't this done?
Comment 8 Andrew Childs 2017-06-22 09:23:25 PDT
The site http://shouldiprefix.com/#transforms suggests that the webkit prefix is still needed for transform, however both transform and transition appear to work fine without a prefix, at least as of 603.1.30. Is there a reason why this bug is still open?
Comment 9 Simon Fraser (smfr) 2017-06-22 10:34:33 PDT
The only thing left prefixed is -webkit-backface-visibility, which needs unprefixing.