- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2023 10:57:21 +0000
- To: public-css-archive@w3.org
noamr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-2] Decide on naming for navigation-triggered view-transition rule == For context, see [TPAC discussion](https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1719751618) as well of the rest of the conversation at #8048. The resolution was that we would have an at-rule that defines the relationship between a navigation and a view-transition - for start, it would allow you to specify that any same-origin navigation results in triggering a view transition. The final naming was left open. Any naming proposal would have to: - convey that this is about navigation-triggered view-transitions - start as "same-origin", in a way that's extendible later to a URL, a pair of URLs, or some other form of conditioning Current suggestions (but open for more!): 1. `@view-transition same-origin { trigger: navigation }` 2. `@view-transition-behavior same-origin { trigger: navigation }` 3. `@navigation-behavior same-origin { view-transition: trigger }` 4. `@nav-transition same-origin { behavior: trigger }` 5. `@view-transition navigation(same-origin) { behavior: trigger }` 6. `@auto-view-transition same-origin { trigger: navigation }` My personal favorite which I've put in the [draft spec](https://github.com/w3c/csswg-drafts/pull/9382) is (3), as it allows extending in the future to other "navigation behaviors" if we so choose, while not being too generic, and tells the story of `if (navigation) { startViewTransition()}`. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9383 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 September 2023 10:57:23 UTC