I wanted to play with view transition in CSS. What do you think?
https://mnt.io
Patch: https://github.com/Hywan/mnt.io/commit/1b123dd3270862f6d2a976c37d91ec45cd0a7711
I wanted to play with view transition in CSS. What do you think?
https://mnt.io
Patch: https://github.com/Hywan/mnt.io/commit/1b123dd3270862f6d2a976c37d91ec45cd0a7711
Introducing view-transitions-mock, a non-visual polyfill for same-document view transitions. @bramus built a spec-compliant JavaScript implementation of the View Transition API that works across all browsers. It handles document.startViewTransition(), the ViewTransition class with its promises, and view transition types. Animations are skipped in unsupported browsers, but DOM updates work as expected. #viewtransition #polyfill
Представляем view-transitions-mock — невизуальный полифил для view transition в рамках документа. Брамус Ван Дамм создал JavaScript-реализацию View Transition API совместимую со спецификацией, которая работает во всех браузерах без кучи условий в коде. Она обрабатывает document.startViewTransition(), класс ViewTransition с промисами и типы View Transition. Обновления DOM идентичны нативным, но анимации пропускаются в старых браузерах. #viewtransition #polyfill
It looks like some basic view transition stuff is finally coming to #Firefox, this demo works in 144 dev edition (stable is now 143): https://mdn.github.io/dom-examples/view-transitions/spa/ or https://6440m.hatchboxapp.com/photos
(but fuck DHH)
If you call `document.startViewTransition()` twice synchronously:
- Chrome: continues applying the first call's transition
- Safari: aborts the first call's transition and throws "AbortError: Old view transition aborted by new view transition."
Chrome's behavior would result in fewer aborted animations, which seems like a good thing. However, Safari's behavior seems like an intentional choice. Which is correct?
The View Transition API is so cool! A cross-page crossfade transition only needs 3 lines of CSS.
https://developer.mozilla.org/en-US/docs/Web/CSS/@view-transition
#Development #Releases
New in Chrome 126 · Cross-document View Transitions for websites are here! https://ilo.im/15z65i
_____
#Chrome #Browser #Website #ViewTransition #CloseWatcherAPI #WebDev #Frontend #CSS #JavaScript
Chrome 126 is rolling out now! With support for cross-document transitions in the ViewTransitions API, the CloseWatcher API re-enabled, trigger-rumbled for the Gamepad API and there's plenty more, and plenty more. Adriana Jara has all the details about what's new for developers in Chrome 126.
#Development #Introductions
What’s new in view transitions? · Get ready for a whole new level of transition animations! https://ilo.im/15ywh8
_____
#Animation #ViewTransition #Webpage #MPA #Browser #WebDev #Frontend #HTML #CSS #JavaScript
#Development #Releases
New in Chrome 124 · Better view transitions, new declarative shadow DOM APIs, and more https://ilo.im/15yl79
_____
#Browser #Chrome #ShadowDOM #WebSocket #ViewTransition #WebDev #WebAPI #Frontend #CSS #JavaScript
Chrome 124 is rolling out now! There are two new APIs that allow the declarative shadow DOM to be used from JavaScript. You can use streams in Web Sockets. View Transitions get a little better. And there's plenty more. Pete LePage has all the details about what's new for developers in Chrome 124.
#Development #Techniques
Handling aspect ratio changes · How to fix CSS view transition animations that look flawed https://ilo.im/15y1me
_____
#Webpage #ViewTransition #Animation #WebDev #Frontend #CSS