:active-view-transition-type() is a lifesaver when you want to isolate different view transition use cases on the same page.
Here is how: vtbag.dev/tips/css/#sc...
Posts by Bag of Tricks for View Transitions
So, Iβve written a bunch of things on how to do certain things with View Transitions, such as optimizing the keyframes or driving a VT by scroll.
I noticed I repeat a lot of code throughout those experiments β¦ so I bundled that all up in a package for you.
π chrome.dev/view-transit...
In light of recent empirical evidence:
Place @view-transition { navigation: auto } exclusively within a <style> element in the <head>.
Refrain from embedding it within external stylesheets, particularly not trailing vast expanses of CSS.
Chrome may otherwise disregard it intermittently.
@view-transition will hopefully be baseline before long
Cool view transition demo by @paolo.ricciuti.me !
yes, that is good news. It is fixed, just not shipped yet. ;-)
No, it is not down to the view transition names or the API level π
In Firefox Nightly, everything already looks like in the first video above π₯ Just a touch of patience and we are there π
Astro v6 just landed, and you can view transition of astro-vtbot from Astro v5 to v6 as a smooth move, simply by letting a version update slide into place.
The new astro vtbot v2.1.12 is ready
and works with both Astro v5 and v6. π
www.npmjs.com/package/astr...
ππππ -ππππππππππ-πππππ: ππππ β πππ
πΊπππ πππππ πππππ, πππ ππππ
vtbag.dev/basics/javas...
Think same document view transitions are supported everywhere?
Think again.
Some older browser versions only support the Level 1 API, or not even that. Bramus's library lets you code against the Level 2 API regardless of native support,...
...much like the Bag's mayStartViewTransition():
If you like Adam's article, you might also want to have a look at vtbag.dev/vector-demo/ and fun-with-view-transitions.pages.dev/episode/7/page
So cool to see such a detailed behind-the-scenes look from someone whose work I really admire!
Here are two more demos with swooping transitions that use the image-pair pseudo for the composition instead of the approach described in the article above.
MPA View Transitions FTW!
Surely thereβs something we can do. π
If you want, you can delay the start of cross-document view transitions by blocking the renderer until the custom elements are defined.
Then the last frame you see is the previous page. After the renderer resumes, the next frame shows the loading page with defined custom elements.
If you want, you can delay the start of cross-document view transitions by blocking the renderer until the custom elements are defined.
Then the last frame you see is the previous page. After the renderer resumes, the next frame shows the loading page with defined custom elements.
What kind of regression did you encounter? Itβs a bit tricky to make out from the video.
I am genuinely confident that Firefox will soon support cross document view transitions. That will make an enormous difference to overall compatibility.
Then it will also soon be possible to detect forward and backward directions without the History or Navigation API.
I am genuinely confident that Firefox will soon support cross document view transitions. That will make an enormous difference to overall compatibility.
Then it will also soon be possible to detect forward and backward directions without the History or Navigation API.
Great article, especially for guiding people through their first steps. It clearly and simply covers everything that really matters.
Quick heads-up: some code blocks look a bit odd because parts of the formatting were rendered as code.
If you have written experimental code that uses the provisional `contain: view-transition` syntax, now might be a good time to switch.
As always also covered in "test your own browser", which also includes the link to the most current spec draft.
View Transition API:
There is a new kid on the block! π
Meet the new `view-transition-scope` property and discover how it helps you avoid name clashes with scoped view transitions.
It gives you a clean way to manage transition names and keeps nested transitions from stepping on each other.
Looks really good, even includes the theme toggle π