Re: [csswg-drafts] [css-view-transitions-1] Size animation should use logical properties. (#9057)

The CSS Working Group just discussed `[css-view-transitions-1] Size animation should use logical properties.`, and agreed to the following:

* `RESOLVED: Close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> vmpstr: This is about animating width and height<br>
&lt;TabAtkins> vmpstr: We currently animate those two props of the ::v-t-group pseudo<br>
&lt;TabAtkins> vmpstr: question was if we should be animatingin inline/block-size instead<br>
&lt;TabAtkins> vmpstr: I don't think it matters, since we're always animating both<br>
&lt;TabAtkins> vmpstr: And they should map to each other<br>
&lt;TabAtkins> vmpstr: So proposal is close no change, but happy to hear other opinions<br>
&lt;emilio> q+<br>
&lt;astearns> ack emilio<br>
&lt;TabAtkins> emilio: It does matter if authors can override<br>
&lt;TabAtkins> vmpstr: The override you specify will override that propery, but the default animation doesn't matter since they're both animated.<br>
&lt;flackr> q+<br>
&lt;TabAtkins> vmpstr: I don't see how the dimension you're overriding changes if we're overriding logical vs physical<br>
&lt;TabAtkins> emilio: If they're also animating writing-mode...<br>
&lt;TabAtkins> emilio: But I agree that sinc eyou're doing both it probably doesn't really matter.<br>
&lt;TabAtkins> emilio: let's say you animate to width:50px and height:100px<br>
&lt;TabAtkins> emilio: If you said vertical writing-mode, the width and height won't change meaning, but what you have on your rule, which may be logical, does<br>
&lt;TabAtkins> vmpstr: True, what you override is observable, but...<br>
&lt;flackr> q-<br>
&lt;TabAtkins> emilio: Right. I think animating physical props are fine tho.<br>
&lt;TabAtkins> khush: We are copying the writing mode over from the element actually doing the animation, fwiw. If you flip the writing mode it'll flip the pseudo's writing mode too.<br>
&lt;fantasai> TabAtkins: Animating writing-mode is weird to do in the first place<br>
&lt;fremy> +1<br>
&lt;TabAtkins> emilio: I think a lot of these animatinos use transforms, which are physical anyway, so I think it's okay to match.<br>
&lt;TabAtkins> fantasai: I also think overall using width/height makes more sense, you're less likely to run into w-m issues<br>
&lt;TabAtkins> astearns: Any other opinions?<br>
&lt;fantasai> fantasai notes that writing-mode is not animatable<br>
&lt;TabAtkins> RESOLVED: Close no change<br>
&lt;TabAtkins> [dbaron says something about th emicrophones)<br>
</details>


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


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

Received on Tuesday, 18 July 2023 15:40:49 UTC