[w3ctag/design-reviews] Other Spec Review: Scoped View Transitions (Issue #1188)

skobes-chromium created an issue (w3ctag/design-reviews#1188)

### 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](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md) intro text
- A description of the problems that end-users were facing before this proposal: [explainer > Motivation](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#motivation)
- Alternatives considered: [explainer > Prior Work](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#prior-work)
- Examples of how to use the proposal to solve the end-users' problems: [explainer > How to use](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#how-to-use)
- What do the end-users experience with this proposal: [explainer > Motivation](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#motivation)
- User research you did to validate the problem and/or design, if any: [VT missing features poll](https://github.com/w3c/csswg-drafts/issues/9890#issuecomment-1927179371); [dev trial](https://groups.google.com/a/chromium.org/g/blink-dev/c/kafnCyjDMrw/m/4XkuFmk7BgAJ)
- Web Platform Tests: [css/css-view-transitions/scoped](https://github.com/web-platform-tests/wpt/tree/master/css/css-view-transitions/scoped)

### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/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](https://github.com/w3c/csswg-drafts/issues/9890)
  - [w3c/csswg-drafts#12324 - Clarify the ::v-t box and stacking context position relative to the scope](https://github.com/w3c/csswg-drafts/issues/12324) (WG resolutions)
  - [other Agenda+ issues](https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue%20label%3AAgenda%2B%20label%3Acss-view-transitions-2) (may see further discussion)

### Feedback so far

- Multi-stakeholder feedback:
  - Chromium comments: [Intent to Prototype](https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67abaada.2b0a0220.1b0c0.01f4.GAE%40google.com)
  - 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](https://github.com/w3c/csswg-drafts/issues/13123)); we currently propose `view-transition-scope: auto`.
- Status/issue trackers for implementations:
  - [Chrome Status](https://chromestatus.com/feature/5109852273377280)

### 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


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

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