CSS view transition auto name generation

[noamr]

こんにちは TAG-さん!

I'm requesting a TAG review of view transition auto name generation.

Generating names for view-transition based on element identity, to reduce burden of inventing unique names.

• Explainer¹: https://github.com/WICG/view-transitions/blob/main/auto-name-explainer.md

• Specification: https://drafts.csswg.org/css-view-transitions-2/#auto-vt-name

• WPT Tests: Still under review (https://chromium-review.googlesource.com/c/chromium/src/+/5878355)

• User research: See poll

• Security and Privacy self-review²: https://github.com/WICG/view-transitions/blob/main/auto-name-explainer.md#self-review-questionnaire-security-and-privacy

• GitHub repo: https://github.com/w3c/csswg-drafts

• Primary contacts: @noamr @khushalsagar, Google, editing the view-transitions spec

• Organization/project driving the specification: Google

• Multi-stakeholder support³:

  • Chromium comments: Supportive (implemented here
  • Mozilla comments: TBD
  • WebKit comments: Generate CSS view-transition-name from element WebKit/standards-positions#408
  • {{...include feedback/review from developers, implementers, civil society, and others}}

• Status/issue trackers for implementations⁴: TBD
  Further details:

• I have reviewed the TAG's Web Platform Design Principles

• Relevant time constraints or deadlines:

• The group where the work on this specification is currently being done:

• The group where standardization of this work is intended to be done (if different from the current group):

• Major unresolved issues with or opposition to this specification:

• This work is being funded by:

You should also know that... this has been discussed thoroughly in the CSSWG.

[martinthomson]

Hi @noamr, I know this is a small thing, but the explainer really needs examples.

[martinthomson]

Discussed in a breakout. This seems fine. There is a web-compat risk "self" and "auto" were not previous proscribed, but now have new meaning.