- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Nov 2023 18:41:59 +0000
- To: public-css-archive@w3.org
What does the event give us that we don't get from URL matching in `@view-transition` and types? Doesn't the example below effectively capture the example in OP?
```css
@view-transition {
navigation: auto;
to: url('destination.html');
type: addFullEmbedName;
}
@view-transition {
navigation: none;
to: url('notransition.html');
}
:root:active-view-transition(addFullEmbedName) #thumbnail {
view-transition-name: full-embed;
}
```
The example also allows adding opaque context (as mentioned in https://github.com/w3c/csswg-drafts/issues/9526) this can be achieved in other ways, e.g. session storage.
If the page really wants to run some JS before the transition capture, couldn't they do so by listening to navigations from the navigation API?
--
GitHub Notification of comment by bokand
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8785#issuecomment-1816914764 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 November 2023 18:42:03 UTC