- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Apr 2025 22:11:23 +0000
- To: public-css-archive@w3.org
https://drafts.csswg.org/css-display/#block-container "A block container establishes a new [block formatting context](https://drafts.csswg.org/css-display/#block-formatting-context) if its parent formatting context is not a block formatting context; **otherwise, when participating in a block formatting context itself, it either establishes a new block formatting context for its contents or continues the one in which it participates**, as determined by the constraints of other properties (such as [overflow](https://www.w3.org/TR/CSS2/visufx.html#propdef-overflow) or [align-content](https://www.w3.org/TR/css-align-3/#propdef-align-content))." According to the suggestion, the injected anonymous block box (a block container box) does not participate in an inline formatting context. If it instead participates in a block formatting context (the only logical alternative) then, per the spec, it must either establish a new block formatting context for its contents or continue an existing one. How this aligns with the fact that its contents are entirely inline is left undefined. -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11461#issuecomment-2843483447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 April 2025 22:11:24 UTC