W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2018

[css-transforms-1] Open issues

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 28 May 2018 04:18:19 +0000
To: www-style list <www-style@w3.org>, public-fx <public-fx@w3.org>
Message-ID: <4E73B50F-D382-4F44-A3DF-A637BD088A1B@adobe.com>
Hi all,

There are a couple of issues in CSS Transforms 1 that require some input from implementers. Ideally we find an agreement before there is a WG discussion about them.

Please take a look at CSS Transform issues in general (https://github.com/w3c/csswg-drafts/labels/css-transforms-1) but more specifically:

1. Smarter interpolation of truncated transform lists (https://github.com/w3c/csswg-drafts/issues/927)
The spec was changed to automatically add missing transform functions at the end of a shorter transform list during interpolation only if the 2 transform lists are compatible otherwise.
The WG resolved to be even smarter and allow per-transform function interpolation for something like
translate(20px, 20px) rotate(45deg) scale(2) -> translate(0, 0) scale(4)
The proposal is to stick to the current spec text which might be closer to what other CSS properties do and is easier and more likely to get implemented.

2. Presentation attribute as start or end value of a CSS transition (https://github.com/w3c/csswg-drafts/issues/2684)
There is no interoperable behavior for a CSS transition from an SVG transform attribute to a CSS specified transform value.
The proposal is to use the normal CSS algorithm for interpolation. If one transform list contains a 3-value rotate(): fall back to matrix interpolation.

Please comment inside the GitHub issues!

Received on Monday, 28 May 2018 04:18:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:59 UTC