Re: [csswg-drafts] [css-display-4] Proposed alternative syntax for reading order (#9923)

The CSS Working Group just discussed `[css-display-4] Proposed alternative syntax for reading order`, and agreed to the following:

* `RESOLVED: close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> rachelandrew: First of 3 reading order issues<br>
&lt;bramus> … 1st one is an alternative syntax to current draft in display-4 and was proposed by brad.<br>
&lt;bramus> … in the issue i have outlined what we are currently doing and brad’s alt proposal<br>
&lt;bramus> … to have a reading ?? property with 3 values<br>
&lt;bramus> … been a few comments on the issue<br>
&lt;TabAtkins> q+<br>
&lt;bramus> … my concern is that it would allow for a global switch into following visual order which we would want to avoid I think<br>
&lt;bramus> … and also it feels quite confusing as it would ask devs to understand a lot about what they are doing, directions and such<br>
&lt;bramus> … anyone else has comments?<br>
&lt;bramus> astearns: is there anything about this that could be salvaged as something good to add?<br>
&lt;bramus> … agree we should not have a global switch<br>
&lt;bramus> iank_: I like the shorter property name<br>
&lt;bramus> dbaron: I thing next issue is about that<br>
&lt;bramus> rachelandrew: yes, separate thing<br>
&lt;bramus> astearns: other comments?<br>
&lt;astearns> ack TabAtkins<br>
&lt;bramus> TabAtkins: was on queue to agree with rachel’s reasoning. we designed it the way it is for  few reasons. making it generic loses those reasons.<br>
&lt;bramus> … i like the current value set<br>
&lt;bramus> astearns: proposed resolution to close no change<br>
&lt;bramus> … concerns?<br>
&lt;bramus> fantasai: which issue?<br>
&lt;bramus> TabAtkins: 9923<br>
&lt;bramus> astearns: objections?<br>
&lt;bramus> RESOLVED: close no change<br>
</details>


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


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

Received on Thursday, 13 June 2024 08:13:04 UTC