- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Feb 2024 13:54:55 +0000
- To: public-css-archive@w3.org
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-writing-modes] The interaction between display:contents and unicode-bidi should be clearly defined and tested == The interaction between the `unicode-bidi` property and `display: contents` should probably be defined more clearly than it is today, and also tested. In at least Chrome, at least some values of `unicode-bidi` work on elements that are `display: contents`. We should both decide what the desired behavior is and make sure there are tests for it. (There may be some behaviors that are clearly defined today because of explicit wording in the spec that was written before `display: contents` existed, but those definitions may not really be what we want.) (This came from [a review comment](https://chromium-review.googlesource.com/c/chromium/src/+/5240082/comment/c34f3b6d_04fd8f6b/) I made on a Chromium CL.) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9897 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 February 2024 13:54:58 UTC