- From: Andy Jakubowski via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Apr 2022 16:08:25 +0000
- To: public-css-archive@w3.org
I think it’s tangentially related, but not exactly the same thing. We know _how_ the root element’s box is laid out. It’s laid out as a block-level box inside the initial containing block. And the CSS WG resolved that the [root element is in flow](https://drafts.csswg.org/css-display-3/issues-wd-2017#issue-3) — it’s listed as a change in [css-display-3](https://www.w3.org/TR/css-display-3/), but not mentioned specifically. I guess technically “A box is [in-flow](https://www.w3.org/TR/css-display-3/#in-flow) if it is not out-of-flow.” covers it? We know that: - The root element’s box is in-flow - The root element always generates a block-level box, because it gets blockified - The root element’s box establishes an independent block formatting context, because it contains floats - When CSS property values of the initial containing block are referenced, they reference the values of the root element (unless otherwise specified, because sometime the body element’s values propagate, too) As far as I was able to determine, there is nothing explicit about the viewport, or the initial containing block establishing a block formatting context. Of course, we know that’s what _actually_ happens in implementations. But I wonder if it would make sense to clarify it now that you can explicitly establish independent block formatting contexts with `flow-root` and flex or grid formatting contexts? -- GitHub Notification of comment by andyjakubowski Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7207#issuecomment-1093047289 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 April 2022 16:08:26 UTC