- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 May 2023 20:59:59 +0000
- To: public-css-archive@w3.org
khushalsagar has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-2] Should ViewTransitions be triggered for browser initiated navigations == There are a class of navigations which are initiated via the browser UI: * Entering a url in the URL bar. * Back/forward buttons in the browser UI. It's unclear whether we should initiate a ViewTransition for these. The worry is that we'd hit navigation paths the current Document doesn't expect. For example, there is no link to the Document the user entered in the URL bar in the contents of the current Document. So the author will need to ensure there is a transition defined between any 2 same-origin URLs. They can always use the cross-fade setup by the UA CSS. If we don't enable ViewTransitions for navigations initiated using the URL bar, it makes handling back/forward slightly complicated. Using back/forward in the browser UI is a common navigation pattern. If A -> B had a ViewTransition, we likely also want one for B -> A triggered by the back button. So we'll have to carve out the subset of cases where back/forward in the UI use ViewTransitions. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8783 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 May 2023 21:00:00 UTC