- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Nov 2023 16:00:35 +0000
- To: public-css-archive@w3.org
Summarizing a conversation today: 1. This seems like a nice-to-have because its pretty easy to polyfill. Authors can use startViewTransition to do an entry animation by starting with a `display: none` DOM. 2. While we want to encourage authors to write custom transitions when navigating between same-origin pages, it's better if cross-origin navigations don't have entry animations on the new Document. This avoids author transitions interacting badly with browser defined transitions. And browser transition makes more sense for cross-origin navigations anyway (since its no longer the experience within one site). Caveat: The spec does allow the UA to skip cross-document ViewTransitions if there is a UA transition that takes precedence. 3. Its going to be rare for same-origin navigations to hit this case, authors will likely design a transition with the old Document in mind. 4. Even if we want to support this case, it should be an explicit opt-in. For example, `from: none` in the opt-in. Authors will be surprised if an opt-in on the new Document also causes entry animations. This opt-in can be added later if we see demand for it. **Proposed Resolution**: View Transition is only triggered when both the old/new Document opt-in. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8791#issuecomment-1799026371 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 November 2023 16:00:36 UTC