- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 17:22:48 +0000
- To: public-css-archive@w3.org
> Would discover tags with just "foo", but then all other stages happen with "foo" and "bar". I don't think this would be the case. We look for the old tags at the very end of the next frame after `startViewTransition`, triggered [here](https://html.spec.whatwg.org/#update-the-rendering:~:text=For%20each%20fully%20active%20Document%20in%20docs%2C%20perform%20pending%20transition%20operations%20for%20that%20Document.). So mutating `types` right after calling `startViewTransition` will ensure its applied to the style cascade when we look for names. > also happen to hit on two opposing sides of animate tag discovery, so they have different effects. This example sounds like working as intended to me? If you updates types in updateCallbackDone promise then it would apply before we discover names in the new DOM. If you update it in the ready promise then it would apply after the pseudo-DOM has already been generated. Is there any behaviour here that sounds unexpected to you? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9526#issuecomment-1812954016 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 November 2023 17:22:49 UTC