- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Nov 2023 09:50:55 +0000
- To: public-css-archive@w3.org
> * `all`: This matches all navigations that are observable with the `navigation` API and is an opt-in. Authors would use this if they are setting up the opt-in via script events (like `navigate`) on the old Document and `activationInfo` on the new Document. > * `none`: This matches all navigations that are observable with the `navigation` API and is an opt-out. > * `auto`: This matches all navigations the author is guaranteed to expect: link clicks/author-initiated (IIUC the spec way to say this would be user navigation involvement != "browser UI") _except_ reload. We're excluding reload based on developer feedback (see [[css-view-transitions-2] Should ViewTransitions be triggered for reloads? #8784](https://github.com/w3c/csswg-drafts/issues/8784)). Based on @domenic's feedback, which I resonate with, I think that for now `auto` should mean "everything except `reload`", and for the time being not try to be more opinionated than that about "browser UI". People can create more precise distinction if they wish using JS. If we get feedback later that some of those browser-UI transitions are unexpected and people do the same thing consistently in JS, we can add new keywords. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8783#issuecomment-1820578485 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 November 2023 09:50:56 UTC