- From: Ian Kilpatrick via GitHub <noreply@w3.org>
- Date: Fri, 30 May 2025 23:22:20 +0000
- To: public-css-archive@w3.org
> > > If the element’s [principal box](https://drafts.csswg.org/css-display-4/#principal-box) is [fragmented](https://drafts.csswg.org/css-break-4/#fragment), [skipped](https://drafts.csswg.org/css-contain-2/#skips-its-contents), or [not rendered](https://drafts.csswg.org/css-images-4/#element-not-rendered), this property has no effect. > > Where the link for 'fragmented' specifically lists block-inside-inline. Two points: - Above refers to the "principle box", e.g. the (potential) anonymous boxes that a UA may insert aren't the "principle box". - The note in the "fragment" definition referring to inline-splitting is looks incorrect based on my undersanding. > As Emilio said, it's not super obvious what the bounding boxes to use would be, so it'd be nice to have some thorough tests of this so we can try to avoid more browser-specific bugs relating to IB splits. Thats somewhat orthogonal however (and maybe requires clarification!). E.g. the geometry of the inline is no different if it has a block-in-inline present or not; and the block-in-inline **should** be painted by the inline. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12217#issuecomment-2923706825 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 May 2025 23:22:22 UTC