[w3ctag/design-reviews] Cross-document View Transitions API (Issue #851)

こんにちは TAG-さん!

I'm requesting a TAG review of Cross-document View Transitions API (css-view-transitions-2).

Cross-document transitions are an extension to [same-document transitions](https://drafts.csswg.org/css-view-transitions-1/), adding the semantics necessary to display transitions when navigating across documents.

  - Explainer¹ (minimally containing user needs and example code): [url](https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.md)
  - User research: N/A
  - Security and Privacy self-review²: https://github.com/WICG/view-transitions/blob/main/security-privacy-questionnaire-cross-doc.md
  - GitHub repo (if you prefer feedback filed there): https://github.com/WICG/view-transitions
  - Primary contacts (and their relationship to the specification): Noam Rosenthal (@noamr), Khushal Shag
     - Noam Rosenthal (@noamr), Google
     - Khushal Sagar (@khushalsagar), Google
     - Vladimir Levin (@vmpstr), Google
     - Tab Atkins (@tabatkins), Google
  - Organization/project driving the design: Google
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5118874666663936

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):
  - The group where standardization of this work is intended to be done ("unknown" if not known):
  - 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:

You should also know that...

See design review for same-document transitions: #748

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

  ☂️ open a single issue in our GitHub repo **for the entire review**

------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Please preview the issue and check that the links work before submitting.

In particular:
* if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer public documents though, since we work in the open.

¹ For background, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/). We recommend the explainer to be in [Markdown](https://github.github.com/gfm/).

² Even for early-stage ideas, a Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.


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

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