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
Reacted by BearCoder, Joseph Saab, matwent, Jake Archibald, Maarten Van Hoof, maxch-aa, firefoxic, Teemu Sillantaus, Harry Theo, Bramus and 96 more
Reacted by Naman Goel and Santi
Reacted by Joseph Saab, Jake Archibald, Sina Salahshour, Pav Sidhu, Houssein Djirdeh, otabekshoyimov, Callie Riggins Zetino, Naman Goel, Chris Coyier, Kris Gray and 16 more
Reacted by Houssein Djirdeh, Chris Coyier, Callie Riggins Zetino, Naman Goel, Kris Gray, Ang Li, Andre Wiggins, Joe Lencioni, Jeduan Cornejo, Kim Nguyen and 5 more
The sheer amount of workarounds and libraries that have been made to enable transitions between layouts speaks for the high demand for View Transitions.
Some of the WORKAROUNDS are below.
In the React world a commonly used library is framer-motion that implements layout animations. When DOM changes, framer-motion will animate the element from the last DOM into the element in the next DOM with the same layout id, effectively retaining a snapshot of a portion of the old page.
Transition libraries, e.g. highway.js, taxi.js, work by orchestrating the inclusion of the DOM of the next page into the current one. For some portion of the time, DOM from both pages is present at the same time allowing for transition animations.
Vanilla implementation for tricky transitions is an option. Again it amounts to handling two DOM states at the same time, and in majority of cases across different pages. History API is used to detect URL changes, but then DOM removal from the old page is delayed until transition is complete.
View Transitions will absolutely ease and speed up implementation of page transitions by allowing developers to focus on transitions themselves instead of dealing with DOM manipulations.
View Transitions will have a positive impact on ACCESSIBILITY.
Preserving two DOM snapshots for the sake of transitions has unpredictable effect on screen readers. Proper implementation requires extra care with attribute management and focus states, which are commonly neglected.
Standardising view transitions will certainly alleviate some of accessibility pain points.
For survey data and web developer demand, in preliminary results from State of HTML 2023, View Transitions was a very common response to the freeform question "Which existing HTML features or browser APIs are you unable to use because of browser differences or lack of support?"
Reacted by maxch-aa, Luke Warlow, otabekshoyimov, Matt McCray, Naman Goel and Rick Byers
Thank you for proposing View Transitions Level 1 for inclusion in Interop 2024.
We wanted to let you know that this proposal was not selected to be part of Interop this year.
This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year if necessary.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!
Activity
maxch-aa commentedon Oct 5, 2023
The sheer amount of workarounds and libraries that have been made to enable transitions between layouts speaks for the high demand for View Transitions.
Some of the WORKAROUNDS are below.
View Transitions will absolutely ease and speed up implementation of page transitions by allowing developers to focus on transitions themselves instead of dealing with DOM manipulations.
maxch-aa commentedon Oct 5, 2023
View Transitions will have a positive impact on ACCESSIBILITY.
Preserving two DOM snapshots for the sake of transitions has unpredictable effect on screen readers. Proper implementation requires extra care with attribute management and focus states, which are commonly neglected.
Standardising view transitions will certainly alleviate some of accessibility pain points.
foolip commentedon Oct 5, 2023
For survey data and web developer demand, in preliminary results from State of HTML 2023, View Transitions was a very common response to the freeform question "Which existing HTML features or browser APIs are you unable to use because of browser differences or lack of support?"
wpt-interop commentedon Feb 1, 2024
Thank you for proposing View Transitions Level 1 for inclusion in Interop 2024.
We wanted to let you know that this proposal was not selected to be part of Interop this year.
This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year if necessary.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!
Posted on behalf of the Interop team.
foolip commentedon Feb 1, 2024