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

> As I understand it, the point of the @view-transition rule as it was initially proposed is to configure under which conditions view transitions should be triggered.
It does not cover different view transitions based on those conditions. If there should be different transitions for different conditions, we need a separate feature to detect that.

Thanks for the feedback @SebastianZ. +1, the point of `@view-transition` rule is indeed to configure which conditions view transitions should be triggered for. We inevitably end up talking about view transition customization (what the animation looks like) here to ensure it works well with the rule. `reload` is especially tricky because we want transitions to be disabled-by-default for them and also allow authors to customize the transition for this case.

> New media features lend themselves to target this use case. Though if we go that route, I'd suggest to keep them general and only bind them to navigation, not view transitions specifically.

Huge +1 to this. Navigation related media feature shouldn't be limited to view transitions. They are a general concept which VT need as a building block since we need to enable authors to use different CSS based on the ongoing navigation.

> So we'd introduce media features like navigation-type: [ reload | push | replace | traverse ], navigation-origin: [ same-origin | cross-origin ] (plus maybe URL patterns) and navigation-mechanism: [ interaction | api ].

Our thinking was to limit media features to cases which need to customize the transition, and for now we've only seen use-cases for `navigation-type`. Were you proposing that every aspect of the navigation (same-document vs cross-document, same-origin vs cross-origin) should be a media feature? As opposed to part of the opt-in at-rule.

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


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

Received on Wednesday, 9 August 2023 17:26:22 UTC