[w3ctag/design-reviews] Disabling UA transitions for same-document navigations (Issue #835)

I'm requesting a TAG review for an API to disable UA transitions for same-document navigations.

Smooth visual transitions as users navigate on the web can lower cognitive load by helping users stay in context. It can also provide a [visual cue](https://www.wired.com/2014/04/swipe-safari-ios-7/) about the destination before initiating the navigation. Both site authors and user-agents (UAs) add visual transitions to their navigations for these use-cases.

However, the user experience is bad if [both the site author and the UA](https://stackoverflow.com/questions/19662434/in-ios-7-safari-how-do-you-differentiate-popstate-events-via-edge-swipe-vs-the) add these transitions: the transitions may conflict and cause confusion for the user. The goal of this proposal is to avoid such cases to ensure only one visual transition is executed at a time.

  - Explainer¹ (minimally containing user needs and example code): [Explainer](https://github.com/WICG/view-transitions/blob/main/default-ua-transitions.md). This review is for the API specified [here](https://github.com/WICG/view-transitions/blob/main/default-ua-transitions.md#choosing-between-ua-and-custom-transition).
  - User research: [url to public summary/results of research]
  - Security and Privacy self-review²: None. The API is limited to same-document navigations.
  - GitHub repo (if you prefer feedback filed there): None. I'd appreciate feedback in comments on this review.
  - Primary contacts (and their relationship to the specification):
      - [Khushal](https://github.com/khushalsagar), Google
      - [William](https://github.com/liuwilliam-gh), Google
  - Organization/project driving the design: Google
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5206595333521408

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): CSSWG
  - The group where standardization of this work is intended to be done ("unknown" if not known): CSSWG
  - Existing major pieces of multi-stakeholder review or discussion of this design:
  - Major unresolved issues with or opposition to this design:
  - This work is being funded by:

The CSSWG issue for discussing this proposal is https://github.com/w3c/csswg-drafts/issues/8747.

If an author chooses to disable UA transitions for a subset of navigations, they will need to use the API proposed at https://github.com/w3ctag/design-reviews/issues/834 to detect whether a UA transition was executed for a navigation.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify [khushalsagar](https://github.com/khushalsagar).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/835
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/835@github.com>