- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 18:03:40 +0000
- To: public-css-archive@w3.org
About the options: note that (4) and (5) are the only ones that guarantee that the types are identical in both documents. I like (4) better than (5) because it's consistent with the rest of the opt-in (both sides have to match). > > 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.). > > > No, but I have the benefit of knowing the implementation. > > Btw, the irony is not lost on me that I claim I know the implementation, but I would get at one case wrong. :) Also, if types change in rAF or in ResizeObserver or in IntersectionObserver, I don't really know if I'm expecting those tags to participate in the transition It affects what's in the `active-view-transition` pseudo-class from that moment on. If you're already running a transition, and you have VT pseudo-elements that rely on `active-view-transition`, they would get affected. This is not different from changing an attribute of the document element mid-transition and relying on that. Which is another use case for this - it lets the author orchestrate a transition by changing types in the middle of the transition using rAF (the same way you would do with changing regular DOM classes). -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9526#issuecomment-1813010887 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 18:03:42 UTC