- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Dec 2020 21:08:42 +0000
- To: public-css-archive@w3.org
Chatted with @emilio about this today, and the problem is the style computation implications of making `direction` pull from the parent box in the case of `marker-side` is too complicated to be practical. `direction` is already an early dependency of most style computation (due to its affecting the cascade of logical properties), and this would make it depend on `marker-side`, `list-style-position`, and `display` as well as the ::marker’s originating element's parent box’s `direction`.
The suggestion here is to instead ask authors to compensate via style rule, and to put the compensation code in an example in the spec:
```
@supports (marker-side) {
X { marker-side: match-parent / list-container / whatever we decide to call it; }
*:dir(rtl) > X::marker { direction: rtl; }
*:dir(ltr) > X::marker { direction: ltr; }
}
```
(Of course all of this can be worked around by having a inner wrapper element to which the direction is applied, rather than setting dir on the list-item itself.)
--
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4202#issuecomment-742800235 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 December 2020 21:08:43 UTC