Other Spec Review: Scoped View Transitions

[skobes-chromium]

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 > Alternatives Considered
• 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: mozilla/standards-positions#1352
  • WebKit comments: WebKit/standards-positions#611
• 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

---

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

[xiaochengh]

Hi @skobes-chromium, the TAG discussed this and are generally positive about this new feature. The motivation is strong, and we didn't identify concerns out of the typical scope of CSS.

We would like to see more alternatives compared in the explainer, though. In particular:

• How does it compare to the status quo?
• Are there other scoping mechanisms considered? For example, shadow-scoping vs. element-scoping

Thanks!

[skobes-chromium]

Thanks @xiaochengh , I've added an Alternatives Considered section to the explainer.

[xiaochengh]

Thanks @skobes-chromium! The TAG are pretty happy with the update and therefore closing it as satisfied.