Re: [csswg-drafts] [css-view-transition] "capture the new state" and "capture the old state" are subtly different. (#11071)

I think it is intentional, the "update pseudo-element styles" algorithm, which is ran on every frame and right after "capture new state", would skip the view transition anyway in this case:

https://drafts.csswg.org/css-view-transitions-1/#update-pseudo-element-styles

> Return failure if any of the following conditions is true:
> * capturedElement’s [new element](https://www.w3.org/TR/css-view-transitions-1/#captured-element-new-element) has a [flat tree](https://drafts.csswg.org/css-scoping-1/#flat-tree) ancestor that [skips its contents](https://www.w3.org/TR/css-contain-2/#skips-its-contents).
> * capturedElement’s [new element](https://www.w3.org/TR/css-view-transitions-1/#captured-element-new-element) is [not rendered](https://www.w3.org/TR/css-images-4/#element-not-rendered).
> * capturedElement has more than one [box fragment](https://www.w3.org/TR/css-break-4/#box-fragment).


Fwiw, this check is mostly there as a technical limitation of engines, but in theory if browsers support snapshotting fragmented content, this check shouldn't be there. WebKit doesn't currently have this check (but mostly because there's no great way to reliably check for fragmented content).

-- 
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11071#issuecomment-2429563146 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 22 October 2024 15:13:51 UTC