- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Feb 2021 05:07:18 +0000
- To: public-css-archive@w3.org
The circularity is not solved. In an annotation container, the `writing-mode` depends on `ruby-position`, but computing `display` depends on `writing-mode`, without figuring out `display` first you don't know it's an annotation container, and without knowing it's an annotation container, you don't know whether `ruby-position` should change the `writing-mode`. It's still a circular dependency between `display`, `writing-mode`, and `ruby-position`. As I should have mentioned before, this isn't strictly unsolvable, because as far as `display: ruby-text-container` can't be changed by `writing-mode`, and nothing else can be computed to `display: ruby-text-container` based on `writing-mode`, it's probably fine. It just feels a bit fishy to have this. But probably it's probably fine. -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1773#issuecomment-774598160 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 7 February 2021 05:07:20 UTC