- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Jan 2019 23:45:58 +0000
- To: public-css-archive@w3.org
@ali-hardan I'm not sure I would rule it out 100%, but it seems doutful:
* `unicode-bidi: plaintext` isn't ancient, but it's not brand new either, and Firefox and Chrome have been supporting it for 2 or 3 years, so there is probably content that depends on the behavior staying the same
* It's a little more complicated, but in effect it boils down to this problem: https://wiki.csswg.org/faq#selectors-that-depend-on-layout. If `unicode-bidi: plaintext` could affect the direction so that the `:dir()` selector could react to it. Selectors changing based on the value of properties isn't possible, because otherwise you could write this, which browsers cannot handle:
```css
div:lang(lrt) { unicode-bidi: plaintext; }
div:lang(rtl) { unicode-bidi: normal; }
```
Maybe it could be made to affect the logical properties at computed value time without affecting the `:dir` pseudo class, as that's not a loop, but having logical properties and `:dir` be inconsistent sounds pretty bad too.
--
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-454207170 using your GitHub account
Received on Monday, 14 January 2019 23:46:00 UTC