Re: [csswg-drafts] [css-overflow-3] 'overflow' 2-value syntax is in wrong order (#2988)

The CSS Working Group just discussed `[css-overflow-3] 'overflow' 2-value syntax is in wrong order`, and agreed to the following:

* `RESOLVED: scroll-snap-align and future 2-axis properties use the logical model`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-overflow-3] 'overflow' 2-value syntax is in wrong order<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2988<br>
&lt;dael> astearns: We talked about this once<br>
&lt;dael> tab<br>
&lt;dael> TabAtkins: Thread conclusion is it was too late to change to block inline ordering. Stick to horz vertical<br>
&lt;dael> TabAtkins: Designed scroll snap align to match. The question, then, is if we can or should switch scroll-snap-align to match or keep with other logical properties<br>
&lt;dael> TabAtkins: fantasai said in issue we have two properties using block already. I suspect right answer is overflow is an unfortunate legacy and leave s-s-a to line up with the logical and suspect other values will be logical in future<br>
&lt;dael> TabAtkins: My preference is s-s-a and future 2 value directional shorthands are logical<br>
&lt;dael> astearns: Comment from David about s-s-a- usage being relatively high<br>
&lt;heycam> q+<br>
&lt;dael> TabAtkins: I was saying we should not change<br>
&lt;dael> TabAtkins: Keep all the current properties logical and align s-s-a with those<br>
&lt;astearns> ack heycam<br>
&lt;dael> heycam: A long time ago there were proposals to have keywords to opt into logical. Would that smooth over the edges of properties we can't change so authors can stay in logical if they stick the keyword in<br>
&lt;dael> TabAtkins: Very possibly. I'm not deep into lore of why we haven't gone with that. Hvae to ask editor on logical properties spec. Could be an encouragement for that model<br>
&lt;dael> TabAtkins: I suggest we resolve s-s-a and future 2-axis properties use the logical model<br>
&lt;dael> astearns: Looking back to see what we resolved originally<br>
&lt;dael> astearns: Logical is what s-s-a uses currently, yes?<br>
&lt;dael> TabAtkins: Yes<br>
&lt;dael> astearns: Any more discussion about the proposal?<br>
&lt;dael> astearns: Prop: s-s-a and future 2-axis properties use the logical model<br>
&lt;dael> astearns: This could be ameliorated by a switch to logical<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: scroll-snap-align and future 2-axis properties use the logical model<br>
</details>


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


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

Received on Wednesday, 1 September 2021 23:12:48 UTC