- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 May 2018 04:03:16 +0000
- To: public-css-archive@w3.org
@AmeliaBR The current WebKit behavior (not returning to attribute value) for sure is a bug. Just thought I'd mention it here as well. I _think_ that the behavior of Edge is a bug too or a compromise for simplicity reasons. Maybe @dstorey or @atanassov know. The [current spec text](https://drafts.csswg.org/css-transforms/#svg-transform-functions) reflects your expectation for the most part I think. I missed to remove the 3-value `rotate()` function from the [primitives transform function](https://drafts.csswg.org/css-transforms/#transform-primitives) list but had the intention to do so. I agree that it should be seen as legacy. Nevertheless (as you seem to agree) it should not just be ignored or reduced to its rotation for interpolation IMO. And yes, I hope we can agree on the behavior that we already have for interpolation between 2 CSS property values and find a solution for the 3-value `rotate()`. The spec text request matrix interpolation if the transform list contains a 3-value `rotate()`. IMO this is might be an extremely rare case anyway but should be clarified since implementations differ. -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2684#issuecomment-392413220 using your GitHub account
Received on Monday, 28 May 2018 04:03:29 UTC