W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [css-transitions] Some matrix-based rotation interpolations are "wrong"

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 6 May 2013 17:31:18 -0700
Message-ID: <CAAWBYDCP01p08rPbx5p2_eq=pAzFmv_ibhrsbKMVi4C49nMDCw@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: www-style list <www-style@w3.org>
On Mon, May 6, 2013 at 5:24 PM, Dirk Schulze <dschulze@adobe.com> wrote:
> Can you elaborate a bit more what you mean with switching to this behavior in Blink? As far as I see it in the source code, Blink and WebKit never did it differently then that. Your example works the same in Chrome as in Safari. I am happy to do the changes to the spec and I agree that they make sense. However, this won't have any affect on the bug mentioned by Rik [1]. We will still need further changes. The editors of Transforms are still trying to figure out what happens in Safari for that.

Please read my email more closely - both Chrome and Safari have the
"short path" behavior on the example as written, but as soon as you
change it so that it uses a slightly different rotation axis, or uses
the matrix3D function either explicitly or via decomposition, Chrome
currently does "long path", while Safari still does "short path".

For example, change the rotation axis in the "to" state to "0, .1, 1",
or add a "translate(1px)" to one of the states, or something else that
forces us into matrix-interpolation rather than argument
interpolation.

~TJ
Received on Tuesday, 7 May 2013 00:32:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 May 2013 00:32:09 UTC