Re: [csswg-drafts] [css-transforms-2] Syntax of individual transforms should reflect general CSS syntax (#7646)

The CSS Working Group just discussed `[css-transforms-2] Syntax of individual transforms should reflect general CSS syntax`, and agreed to the following:

* `RESOLVED: undo previous resolution, do not add the longhands to the rotate, translate, and scale properties`

<details><summary>The full IRC log of that discussion</summary>
&lt;florian> dbaron: I don't see a whole lot in terms of usecase<br>
&lt;florian> dbaron: it seems we want to do this for completeness and consistency<br>
&lt;florian> dbaron: but the cost seems high<br>
&lt;florian> dbaron: because you need to support animating them on separate timelines<br>
&lt;florian> dbaron: not theoretically hard, but adds complexity to a performance sensitive path<br>
&lt;florian> dbaron: would be ok given strong use cases, but otherwise, the cost might be too much<br>
&lt;hober> q+<br>
&lt;florian> TabAtkins: we'd go from 3 properties to 7<br>
&lt;florian> hober: I share dbaron 's concern, but would defer to simon if he has an opinion<br>
&lt;florian> dbaron: not absolutely opposed to doing this, but want a stronger justification than has been given so far, given the cost<br>
&lt;florian> bramus: I remember requests, but not what the motivating use case was.<br>
&lt;florian> Rossen_: the proposal is to revert the previous resolution<br>
&lt;florian> RESOLVED: undo previous resolution, do not add the longhands to the rotate, translate, and scale properties<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1646221413 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 21 July 2023 20:47:31 UTC