Re: [csswg-drafts] [css-view-transitions-1] How do the writing-mode and direction properties affect the view-transition pseudo-elements? (#8230)

The CSS Working Group just discussed `[css-view-transitions-1] How do the writing-mode and direction properties affect the view-transition pseudo-elements?`, and agreed to the following:

* `RESOLVED: Copy text-orientation from the dom node, along with the existing writing-mode/direction.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> khush: This also came up in i18n review<br>
&lt;TabAtkins> khush: this is one case where direcitonality matters<br>
&lt;TabAtkins> khush: when you're animating an element, morphing from one shape to another...<br>
&lt;TabAtkins> khush: The animation tries to make it so if the a-r of the box changes, in the inline direction the snapshot stretches to match the final size<br>
&lt;TabAtkins> khush: And the block matches the aspect ratio<br>
&lt;TabAtkins> khush: so whether it gets cover or contain behavior depends on snapshot a-r<br>
&lt;TabAtkins> khush: To make it work this way, we have the group animate width and height<br>
&lt;TabAtkins> khush: And the element inside use inset-block-start: 0, inline-size:100%, and block-size:auto<br>
&lt;TabAtkins> khush: for this setup to work, there has to be a writing mode, we copy those from the dom element ot the group<br>
&lt;TabAtkins> khush: Are these two properties enough? do we need text-orientation as well?<br>
&lt;TabAtkins> khush: It seems like the effect of text-orientation is baked into the snapshot, so we don't need it for this animation to work<br>
&lt;TabAtkins> khush: fantasai had a point about how it interacts with cascade<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> fantasai: yeah text-orientation can change which logical and physical map to each other<br>
&lt;TabAtkins> fantasai: It won't affect the properties we are setting in the spec, it can have an impact on what the author sets<br>
&lt;TabAtkins> fantasai: So to get that correct we shoudl copy over all three props<br>
&lt;TabAtkins> khush: I'm fine with copying over all three. Our defaults aren't affected, so if it helps authors it sounds okay<br>
&lt;TabAtkins> astearns: So proposed resolutio is to add text-orientation to the writing-mode/direction properties that we copy from the dom element<br>
&lt;TabAtkins> RESOLVED: Copy text-orientation from the dom node, along with the existing writing-mode/direction.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8230#issuecomment-1640496127 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:52:11 UTC