- From: Dirk Schulze <dschulze@adobe.com>
- Date: Fri, 17 Feb 2012 10:30:08 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Aryeh Gregor <ayg@aryeh.name>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
On Feb 17, 2012, at 10:08 AM, Tab Atkins Jr. wrote: > On Fri, Feb 17, 2012 at 9:57 AM, Dirk Schulze <dschulze@adobe.com> wrote: >> I still believe that the interfaces for CSS Transforms are really useful. And I would be happy to work on that and see it for CSS Transforms. But it feels like these changes are not widely accept because of following reasons: >> >> * People are afraid that it could block CSS3 Transforms to reach CR soon. >> >> * Some discrepancies how to deal with DOM2 (getPropertyCSSValue() and CSS*Value) and how to improve CSSOM API. >> >> Maybe we can find a compromise: >> >> Remove CSSTransformValue and CSSMatrix from the current spec like proposed by Simon Fraser, Boris Zbarsky and Aryeh (who was unsure about CSSMatrix). >> >> Work on an interface (CSSTransformList, CSSTransform(Value), CSSMatrix or what ever) for CSS4 Transforms. This interface would give authors direct access to modify transformation functions. > > That's less a compromise and more "exactly what those of us who want > to advance the spec quickly want". ^_^ So yes, I approve. Hehe, so far the discussion was just about removing stuff. Not delaying it, with the will to work on that on the next level of the spec as far as I understood it. -Dirk
Received on Friday, 17 February 2012 18:30:42 UTC