Very exciting news! This is the thing that gives Custom Properties their SUPERPOWERS.
Yes, you can use them to enforce type safety, limit their inheritance, and set up a default but what I like most about them is that YOU CAN ANIMATE/TRANSITION REGISTERED CUSTOM PROPERTIES.
@bramus so this issue is affecting Chrome and Safari implementations - is it likely to affect the Firefox one too, or is there a chance they have solved the problem or that it was never a problem for their compositor?
📣 PSA: Time to update your MPA View Transitions demos!
The opt-in for Cross-Document View Transitions for MPA is done by means of the @view-transition at-rule in CSS.
The meta tag from before was a temporary thing while the feature was still being developed behind a flag. The meta tag no longer does anything, you need the CSS opt-in.
@bramus Waow, I had no clue the currently available ViewTransition API was limited to SPA. I’m glad I didn't tried it earlier, I would have been very disappointed. 🤣 Weird this info never reached my brain.
Question: if {current doc} has the <meta> but {next doc} does not, does it mean the browser needs first to fetch the CSS on top of the HTML and then will be like “well, no transition”, which would lead to a slower navigation? With <meta>, the discovery is way faster, no? 🤔
Come hear @mia and me talk about some CSS/web things.
I'll be covering Cross-Document View Transitions for Multi-Page Applications (aka: "just websites") or maybe Scroll-Driven View Transitions which combines two of my favorite topics … still undecided. https://social.vasilis.nl/@vasilis/112444587000998568
What's new in view transitions? (Google I/O 2024 update)
In this video I introduce you to cross-document view transitions for MPA along with two improvements that allow you to more easily work with view transitions in general.