Better not sit in the first few rows when that day comes 😅

Did he bring his flamethrower? 👀 🔥

Arent CAPS for yelling?

Oh no! Take care and get well soon!

And now I'm watching this … 😄

* hums the Jurassic Park theme *

For Cross-Document VTs there is no such property (yet).

We are considering of simply skipping the VT by default in case there was a UA-provided transition (such as a "swipe to go back"). Or would you want this skipping to be opt-in?

For Same-Document View Transitions you can check for hasUAVisualTransition on the event and then skip the VT based on that.

developer.chrome.com/docs/web-pla...

We have something brewing for this … 😉

/cc @nomster.bsky.social @dbaron.org

Perfect! You’ll also be able to find me in the 6PS office the day before :)

Thank you, Kind Sir – It’s not only View Transitions or a Scroll-Driven Animations up my sleeve 😅

(But maybe I could try and sneak some into the talk 😛)

There sure are benefits to using frameworks in the short term, but in the long term you’re bound to hit a wall.

It’s a consideration you have to make: how fine are you with the constraints? You seem experienced enough to gauge that and understand the implications, but there are also many people blindly using a framework (as some sort of cargo-cult) without even realizing that there are constraints.

It’s all fun and games until you want to start coloring outside of the lines. Some frameworks allow you to, but many – especially those the farthest away from the underlying language/technology/paradigms – don’t.