View Transitions API Level 1

[khushalsagar]

Request for position on an emerging web specification

Information about the spec

• Spec Title: View Transitions API Level 1
• Spec URL: https://drafts.csswg.org/css-view-transitions-1/
• GitHub repository: https://github.com/WICG/view-transitions
• Issue Tracker (if not the repository's issue tracker): https://github.com/WICG/view-transitions/issues
• Explainer (if not README.md in the repository): https://github.com/WICG/view-transitions/blob/main/explainer.md

Design reviews and vendor positions

• TAG Design Review: View Transitions API w3ctag/design-reviews#748
• Mozilla standards-positions issue: View Transitions API mozilla/standards-positions#677

Bugs tracking this feature

• WebKit Bugzilla: https://bugs.webkit.org/show_bug.cgi?id=259055
• Radar:

Anything else we need to know

The spec still has some open issues but the overall feature design is concrete at this point. Also here is the chrome status entry.

[khushalsagar]

Heads up, we'll have a session on this feature at TPAC on Wednesday. I'll post the exact time next week. Looking forward to see folks interested there!

[khushalsagar]

The breakout session is on September 14 at 3 PST. Details are here including a link to join virtually.

[fwebdev]

Any results from the TPAC Session on this Topic?

[astearns]

@fwebdev https://www.w3.org/2022/09/14-pagetransitions-minutes.html

[gugadev]

Is there some update about the WebKit’s position on this?

[smfr]

WebKit supports the proposal. We will mark as Support one week from now, pending objections.

[rik]

Can someone with the permission to update the issue rename the specification in the original post to use "View Transitions"? This will help search for it on https://webkit.org/standards-positions/

[annevk]

Thanks for noticing that @rik. I fixed it.

[bokand]

FYI: In Chromium we're planning to split out some of the pieces of cross-document view transitions to ship separately where it makes sense. Specifically we're currently looking at the pagereveal event.

I want to confirm if WebKit is ok with us using the overall signal for view transitions as the position for those pieces? Maybe a bigger question: should we file a new position request for cross-document view transitions as a whole (i.e. view-transitions API level 2) or is this position sufficient (FWIW Mozilla's reusing the same position for both but thought I'd ask) @nt1m @smfr

[nt1m]

It would be good to file new positions for these.