- From: J. S. Choi via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 May 2025 01:02:55 +0000
- To: public-css-archive@w3.org
> I don't understand the connection between the two halves of this sentence. Cross-document transitions can be seen with JavaScript just as easily as same-document transitions, using NavigateEvent's hasUAVisualTransition. @domenic: Yes, sorry, you’re right; I misspoke here. (Cross-document transitions were strongly coupled in my mind to CSS-only, no-JavaScript solutions, but of course that’s not necessarily true.) I’ve crossed out that sentence in the comment. To sharpen my first question: In Safari 18.4, sliding to navigate back in history does seem to suppress author-provided cross-document transitions. But I could not confirm whether this “don’t do a cross-document transition if a visual transition was already done by the user agent” behavior is actually specified anywhere in [CSS View Transitions Level 2](https://drafts.csswg.org/css-view-transitions-2/). (It’s also still worth asking whether a new issue for “an API which lets the author specify whether they prefer to override a navigation transition”—i.e., the bulk of [default-ua-transitions.md](https://github.com/WICG/view-transitions/blob/main/default-ua-transitions.md)—is worth opening. Alternatively, this issue could be reopened.) -- GitHub Notification of comment by js-choi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8333#issuecomment-2864807146 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 May 2025 01:02:57 UTC