Re: [csswg-drafts] [css-view-transitions-1] Should block-in-inline splitting prevent `view-transition-name` from being used (#12217)

> > Note: [box fragment](https://drafts.csswg.org/css-break-4/#box-fragment) here does not refer to fragmentation of [inline boxes](https://www.w3.org/TR/CSS2/visuren.html#inline-boxes) across [line boxes](https://www.w3.org/TR/CSS2/visuren.html#line-box). Such inlines can participate in a transition.
> 
> If an inline gets fragmented it can still participate in a view-transition.

This is what I'm seeking to clarify here. The above wording seems to be quite specific to the fragmentation of an inline across the line box, and any other cases are covered by:
>>  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.

If the intent is to allow this case, then I think the spec should be more clear as to what types of fragments are included/excluded.

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.

-- 
GitHub Notification of comment by mattwoodrow
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12217#issuecomment-2921469102 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 07:27:11 UTC