- From: Oriol via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2017 18:23:37 +0000
- To: public-css-archive@w3.org
But after #1550 I don't think this is only a css-contain problem. Now if `flow` ends up establishing a BFC that's via becoming a formatting context, and I don't see why it should be different for `ruby`. So if you float a ruby then it also becomes a formatting context. If you use `overflow: hidden` on a block-level ruby it also becomes a formatting context. If you make a ruby be a flex or grid item it also becomes a formatting context. Now I'm more convinced that this should be explained by adding a new inner display type: `ruby-root`. Becoming a formatting context would switch `ruby` to `ruby-root` at used-value time. Exposing this inner display type in `<display-inside>` syntax is not necessary, for the moment it could be kept as an internal thing of the spec. This should all be CSS Display things, then in CSS Contain you can decide whether `contain` applies to ruby or whether the ruby is blockified when contained. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-320523481 using your GitHub account
Received on Sunday, 6 August 2017 18:23:38 UTC