Specification

https://drafts.csswg.org/css-view-transitions-2/

Explainer

https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md

Links

• Previous early design review, if any: N/A
• An introduction to the feature, aimed at unfamiliar audiences: explainer intro text
• A description of the problems that end-users were facing before this proposal: explainer > Motivation
• Alternatives considered: explainer > Prior Work
• Examples of how to use the proposal to solve the end-users' problems: explainer > How to use
• What do the end-users experience with this proposal: explainer > Motivation
• User research you did to validate the problem and/or design, if any: VT missing features poll; dev trial
• Web Platform Tests: css/css-view-transitions/scoped

The specification

• Follows the Web Platform Design Principles.
• Includes Security and Privacy Considerations sections based on answers to the Security/Privacy Questionnaire.

Where and by whom is the work is being done?

• GitHub repo: https://github.com/w3c/csswg-drafts
• Primary contacts:
  • @skobes-chromium, Google, author
  • @vmpstr, Google, author
• Organization/project driving the specification: Google
• This work is being funded by: Google
• Primary standards group developing this feature: CSSWG
• Group intended to standardize this work: CSSWG
• Incubation and standards groups that have discussed the design:
  • w3c/csswg-drafts#9890 - Element-scoped view transitions
  • w3c/csswg-drafts#12324 - Clarify the ::v-t box and stacking context position relative to the scope (WG resolutions)
  • other Agenda+ issues (may see further discussion)

Feedback so far

• Multi-stakeholder feedback:
  • Chromium comments: Intent to Prototype
  • Mozilla comments: TBD <!-- And/or other places they've given feedback -->
  • WebKit comments: TBD <!-- And/or other places they've given feedback -->
• Major unresolved issues with or opposition to this specification:
  • At this time the CSSWG has not resolved on the name of the containment API (w3c/csswg-drafts#13123); we currently propose view-transition-scope: auto.
• Status/issue trackers for implementations:
  • Chrome Status

You should also know that...

No response

<!-- Content below this is maintained by @w3c-tag-bot -->

---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1188