- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Oct 2023 17:50:27 +0000
- To: public-css-archive@w3.org
Thanks @dbaron, let me try to summarize. The extension points we see to this are what you mentioned: - qualifying based on URL patterns - qualifying on navigation types (back/forward/reload etc) - extending to declare transition types. Option 8 above is simply that, it says that * means "any transition type". To answer your other question, this is currently being triggered by cross-document navigations only, but an extension point could be enabling this for same-document navigations via the navigation API. My thought about that in particular is that it would probably not belong in CSS, but rather by some sort of JS opt-in that enables CSS navigation-triggered transitions for same-document navigaiton-API navs. It would be awkward if the author had the word `cross-document` sprinkled all over the CSS, and when we allow same-document navigations they would have to rename everything. So in short, this is about navigation-triggered view-transitions, where *at this point* it's enabled only for cross-document. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9383#issuecomment-1773153833 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 October 2023 17:50:29 UTC