- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Oct 2024 16:30:37 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-inline-3] Allow re-ordering of <text-edge> keywords`, and agreed to the following: * `RESOLVED: we allow mix-and-match syntax for <text-edge> keywords` <details><summary>The full IRC log of that discussion</summary> <matthieud> fantasai: a question about syntax<br> <matthieud> fantasai: currently syntax requires the first keyword for the top- dge and second for bottom edge<br> <matthieud> fantasai: we could change the syntax to be re-orderable<br> <matthieud> fantasai: cap and ex are always on top side<br> <matthieud> fantasai: alphabetic always on bottom<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/10713#issuecomment-2285261024<br> <matthieud> fantasai: it could be more explicit and reorderable<br> <matthieud> fantasai: we could also change the keywords to be more explicit<br> <matthieud> fantasai: does it makes a better syntax ?<br> <fantasai> "text ideographic" vs "text-top ideographic-bottom"<br> <matthieud> fantasai: example "text ideogrpahic" is less clear than "text-top ideographic-bottom"<br> <kizu> q+<br> <matthieud> fantasai: choices : no change ? switch to explicit keywords syntax ? allow both syntax (because no ambiguity) ?<br> <fantasai> https://www.software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cp%20style%3D%22font-size%3A%2040px%22%3E%0ATest%0A%3Cspan%20style%3D%22border-top%3A%20solid%20orange%3B%20vertical-align%3A%20text-top%3B%20display%3A%20inline-block%3B%20width%3A%2010px%22%3E%3C%2Fspan%3E%0A%3Cspan%20style%3D%22border-bottom%3A%20solid%20orange%3B%20vertical-align%3A%20text-bottom%3B%20display%3A%20inlin<br> <fantasai> e-block%3B%20width%3A%2010px%22%3E%3C%2Fspan%3E<br> <fantasai> https://www.software.hixie.ch/utilities/js/live-dom-viewer/saved/13205<br> <matthieud> kizu: i like order independance<br> <matthieud> kizu: could we do the same for `position-area` ?<br> <Rossen16> ack kizu<br> <matthieud> kizu: if we can disambiguate it makes sense to make them re-ordereable<br> <bramus> scribe+<br> <bramus> matthieud: it is always implied, no? Trying to summarize<br> <matthieud> fantasai: so kizu is voting for the third choice (mix and match)<br> <fantasai> scribe+<br> <fantasai> matthieud: Can decide at parsing time?<br> <fantasai> fantasai: right<br> <matthieud> RESOLVED: we allow mix-and-match syntax for <text-edge> keywords<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10713#issuecomment-2417335002 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 October 2024 16:30:38 UTC