W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

[csswg-drafts] [css-transforms-1] How precise can we be about serialization? (#4841)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Fri, 06 Mar 2020 20:45:42 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-577166698-1583527541-sysbot+gh@w3.org>
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-transforms-1] How precise can we be about serialization? ==
So as part of some tests I'm writing, I'm using `transform: rotate(90deg);` and testing the serialization. As specified, at computed/used time this becomes a `matrix()`; no problem.

However! In Firefox, a 90deg rotation like that produces the nice, simple serialization of `matrix(0, 1, -1, 0, 0, 0)`. In Chrome, it instead gives `matrix(6.12323e-17, 1, -1, 6.12323e-17, 0, 0)`, aka two of the zeros are instead incredibly small non-zero values.

These two matrixes don't produce a rendering difference, but it sure makes it difficult to test serialization. How precisely do we want to specify this kind of thing? How do browsers *test* their own serialization in the face of issues like this?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4841 using your GitHub account
Received on Friday, 6 March 2020 20:45:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC