Intent to Ship: CSS Transforms unprefixed

Showing 1-7 of 7 messages
Intent to Ship: CSS Transforms unprefixed Douglas Stockwell 4/1/14 10:41 PM

Spec

WD: http://www.w3.org/TR/css3-transforms/

ED: http://dev.w3.org/csswg/css-transforms/


Summary

CSS Transforms were announced in WebKit on the Surfin’ Safari blog in 2007. Usage of -webkit-transform is now approaching 50% of page loads. Given the prevalence of -webkit-transform there was even a time when Opera experimented with -webkit-transform in Presto. Now transforms are shipping unprefixed in IE and Firefox. The CSSWG also gives their blessing.


Link to “Intent to Implement” blink-dev discussion

No formal “Intent to Implement”, however there was discussion on this thread.


Is this feature supported on all five Blink platforms (Windows, Mac, Linux, Chrome OS and Android)?

Yes.


Compatibility Risk

Internet Explorer and Firefox ship roughly interoperable implementations. Manual testing of the 928 tests in the W3C test suite revealed some differences between our implementation and Firefox.


As noted earlier on blink-dev, there are some compatibility issues related to matrix decomposition and transform-style that are still under discussion by the CSSWG.


OWP launch tracking bug?

https://code.google.com/p/chromium/issues/detail?id=154772


Link to entry on the feature dashboard

http://www.chromestatus.com/features/6437640580628480

Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Eric Seidel 4/1/14 10:50 PM
LGTM!
Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Darin Fisher 4/1/14 10:52 PM
LGTM2
Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Adam Barth 4/1/14 10:57 PM
That speadsheet is amazing.  For reference, here are the bugs linked from the speadsheet:

https://code.google.com/p/chromium/issues/detail?id=282226

We should fix those bugs and converge with other browsers, but the bugs don't seem serious enough to block unprefixing.  LGTM.

Adam
Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Dirk Schulze 4/2/14 1:12 AM
928 tests seem to be many. In reality these tests just test a specific subset of CSS Transforms: 2D transforms on SVG content.  Which makes less than a quarter of the spec. Contributing tests is more than welcome!

Many of the spec requirements are simply not implemented for SVG in Firefox, Chrome or IE.

This is why you see so many “matching” behaviors between Firefox and Blink. Therefore, to color the column green is highly misleading. The implementations are just behind the spec.

Greetings,
Dirk
Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Adam Barth 4/2/14 10:03 AM
On Wed Apr 02 2014 at 1:12:41 AM, Dirk Schulze <dsch...@chromium.org> wrote:
928 tests seem to be many. In reality these tests just test a specific subset of CSS Transforms: 2D transforms on SVG content.  Which makes less than a quarter of the spec. Contributing tests is more than welcome!

Many of the spec requirements are simply not implemented for SVG in Firefox, Chrome or IE.

This is why you see so many “matching” behaviors between Firefox and Blink. Therefore, to color the column green is highly misleading. The implementations are just behind the spec.

That's fine though.  As long as browsers behave the same way, we can all make progress together.

Adam
Re: [blink-dev] Intent to Ship: CSS Transforms unprefixed Alex Russell 4/2/14 11:25 AM
LGTM3


LGTM2
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.