Are these APIs web standards? I.e. if I build view transitions for Chrome will they work in Safari when they add the feature? I ask because I've already built a site using the tag view transition implementation and now it looks like this is going to be replaced by CSS directives. Ideally I don't want to have to change my code until this is all settled. Any idea when a consensus will be reached?
The thing with the meta tag you implemented back in the day was part of a prototype which was only available behind an experimental feature flag in Chrome. It lead up to what is now shipping in Chrome, which is part of the View Transitions Level 2 CSSWG web standard. To change your experimental implementation to the standardized one, swap out the meta tag by the at-rule to opt-in. All the rest stays the same. View Transitions are the perfect candidate for Progressive Enhancement: once other browser vendors also implement Cross-Document View Transitions, they too will start showing the transitions. Until then, users get the experience without View Transitions.
@@KhushalSagar Thanks for the reply. I don't know if you are an expert on View Transitions but in case you are - please can you explain something to me: if the view-transition is now triggered by a CSS rule, does this mean that now, all the linked CSS files are preloaded before the new page is displayed, rather than streamed in? I suppose I should expect this because if they aren't loaded, the transition won't know where to transition elements to... Can you clarify please? Or point me in the direction of somewhere this is explained. Thanks :)
@@bramus Thanks for the reply. I wondered if you could please can you please clarify something to me: if the view-transition is now triggered by a CSS rule, does this mean that now, all the linked CSS files are preloaded before the new page is displayed, rather than streamed in? I suppose I should expect this because if they aren't loaded, the transition won't know where to transition elements to... Can you clarify please? Or point me in the direction of somewhere this is explained. Thanks :)
Was fixed to use View Transitions? Trying View Transitions with an embedded RU-vid video playing was not smooth, it refreshed the whole on the target screen.
Does this work with different CSS files for each page? Ik the other version of this API didn't work with different CSS which was a deal breaker for me.
Yes, you can have different CSS files on each page. I'm not sure what you mean by "the other version of this API didn't work with different CSS". Could you clarify?
Flutter don't need this. Cause flutter web app routing is a single client side Virtual Rendered canvas. I guess its just a SPA that has some shallow routing
@@forno_nicolas Actually, Flutter can benefits from this, since people can have MPAs that contains different canvas ctx on each. I have tried something like this, and it worked pretty well.
