- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Oct 2022 23:41:12 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor] Different grammars per axis is not compatible with logical props == https://drafts.csswg.org/css-anchor-1/#anchor-pos > The physical [`<anchor-side>`](https://drafts.csswg.org/css-anchor-1/#typedef-anchor-side) keywords (`left`, `right`, `top`, and `bottom`) must only be used in [inset properties](https://drafts.csswg.org/css-logical-1/#inset-properties) corresponding to the same axis: for example, [`top`](https://drafts.csswg.org/css-anchor-1/#valdef-anchor-top) and [`bottom`](https://drafts.csswg.org/css-anchor-1/#valdef-anchor-bottom) are valid in [`top`](https://drafts.csswg.org/css-position-3/#propdef-top) and [`bottom`](https://drafts.csswg.org/css-position-3/#propdef-bottom), but not in [`left`](https://drafts.csswg.org/css-position-3/#propdef-left) and [`right`](https://drafts.csswg.org/css-position-3/#propdef-right). Using wrong-axis keywords makes the function invalid. But logical properties share the grammar and the computed value with the physical properties, so how does that work? All longhands in a logical property group must have the same grammar. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7847 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 October 2022 23:41:14 UTC