Re: [csswg-drafts] [css-view-transitions-2] Declarative opt-in for cross-document navigations (#8048)

Following up on the F2F, this is the current suggestion including "future" features, based on the feedback from the f2f:

```css
@view-transitions {
  /* default: none. Same-document is a potential future feature. */
  navigation-trigger: cross-document | same-document | any | none;

  /* If present on both sides, has to match, and affects transition-names/media-query */
  /* pending decision on view-transition-groups etc. */
  group-name: foobar;

  /* If present on either, has to match */
  version: 1234;
}
```

To match navigations, the rule would have extra pseudo-classes, equivalent to page rules, e.g.:
```css
@view-transitions :navigating(from --articles) {
  group-name: from-articles;
}
```

In addition, the rule can be nested inside any media-query:
```css
@media (prefers-reduced-motion: no-preference) {
  @view-transitions {
    navigation-trigger: cross-document;
  }
}
```

To support same-site in the future, the idea is that we would want the developer to be explicit about which origins are allowed rather than a blanket `same-site`.

For the current set of features, this is how it would look like when you want to enable MPA transitions:
```css
@auto-view-transitions { 
  navigation-trigger: cross-document;
}
```

-- 
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1644055204 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 20 July 2023 14:43:27 UTC