Re: [csswg-drafts] [css-transforms] Let 'transform-origin' and 'transform' take comma-separated lists (#589)

The CSS Working Group just discussed `Let 'transform-origin' and 'transform' take comma-separated lists`, and agreed to the following:

* `RESOLVED: Reject this proposal`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Let 'transform-origin' and 'transform' take comma-separated lists<br>
&lt;dael> github:<br>
&lt;dael> smfr: Old proposal to allow transform property tot ake a comma sep list where each has its own transform-origin. Additionally a proposal for shorthand to allow origins<br>
&lt;dael> smfr: Seems a bit too late to add this, big change to transform. Not in favor, but welcome other input<br>
&lt;dbaron> Seems like a bunch of complexity (e.g., with animations), so I'm fine with rejecting the proposal.<br>
&lt;dael> TabAtkins: Reasonable. To address use case might be interesting to expore transform-origin function that takes the list. But that would be convenience feature.<br>
&lt;dael> TabAtkins: I was in favor back in the day, but I agree it's minor and not worht the churn<br>
&lt;dael> AmeliaBR: Agree with TabAtkins . If we do this it has to apply to transform-box as well as transform-origin<br>
&lt;dael> astearns: Is what the proposal requests possible but in a different way?<br>
&lt;dael> TabAtkins: Yeah, transalte-origin is a translate function before and after your transform list. You can simulate it on your own. You have to know how to do that and perhaps an example would be good. Nothing to prevent you from representing on your own<br>
&lt;dael> astearns: Proposal is to reject this proposal<br>
&lt;dael> astearns: Concerns?<br>
&lt;dael> RESOLVED: Reject this proposal<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 23 October 2019 16:56:14 UTC