You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an opportunity to share the status of two future-looking enhancements that are in the long term pipeline for view transitions, and are in their early design phase:
gesture-based view transitions: using a preemptive navigation gesture (swipe) to trigger a view-transition
cross-origin view transitions: finding a secure way to allow a subset of what's possible with view transitions to a navigation between two origins that don't necessarily trust each other.
Session goal
Introduce the thinking behind the two future enhancement, and gather early stage feedback, pushback, and hopefully enthusiasm!
Since these features touch on UX, navigations, performance and security, they could be of interest to people outside the CSS working group.
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.
Session description
This is an opportunity to share the status of two future-looking enhancements that are in the long term pipeline for view transitions, and are in their early design phase:
Session goal
Introduce the thinking behind the two future enhancement, and gather early stage feedback, pushback, and hopefully enthusiasm!
Since these features touch on UX, navigations, performance and security, they could be of interest to people outside the CSS working group.
Additional session chairs (Optional)
@khushalsagar
Who can attend
Anyone may attend (Default)
IRC channel (Optional)
#css
Other sessions where we should avoid scheduling conflicts (Optional)
#43
Instructions for meeting planners (Optional)
No response
Agenda for the meeting.
No response
Links to calendar
Meeting materials
The text was updated successfully, but these errors were encountered: