- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Dec 2023 15:39:25 +0000
- To: public-css-archive@w3.org
> The spec says [here](https://drafts.csswg.org/css-view-transitions-1/#capture-the-old-state) that the iteration on elements should be according to paint order. That doesn't really answer my question. I'm talking about step 4.6 of "capture new state": > [For each](https://infra.spec.whatwg.org/#list-iterate) element of every [element](https://drafts.csswg.org/css2/#element) that is [connected](https://dom.spec.whatwg.org/#connected), and has a [node document](https://dom.spec.whatwg.org/#concept-node-document) equal to to document, in [paint order](https://drafts.csswg.org/css2/#painting-order): > [...] > * If namedElements[transitionName] does not [exist](https://infra.spec.whatwg.org/#map-exists), then set namedElements[transitionName] to a new [captured element](https://drafts.csswg.org/css-view-transitions-1/#captured-element) struct. If `namedElements[transitionName]` does not exist, then where in the map do we set this new struct? By default it will be at the end of the map, and it doesn't matter in which order you iterate. I'm aware that case is a super edge case, because most of the map will be populated by "capture old state", in the right order, but where the step 4.6. of "capture new state" appends in the map makes a difference. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9672#issuecomment-1838907482 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 December 2023 15:39:27 UTC