Cross-origin view transitions

[noamr]

Session description

Cross-document view transitions were built with same-origin navigations in mind, as a lot of information is shared between documents in order to perform the full set of same-document view transitions.

In this session, we'll explore trade-offs that would let us grab some of the expressiveness of the existing view transitions, and enable that kind of smooth experience for cross-origin navigations, while keeping the security challenges in check.

Session goal

Introduce and explore cross-origin view transitions, proposal and alternatives

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#css

Other sessions where we should avoid scheduling conflicts (Optional)

#47, #57

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

No response

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[khushalsagar]

List of sessions to avoid a conflict with:

• Canvas place element #43
• View transitions: a taste of the future #47

[noamr]

Closing, merging this one with #47.