Some personal news, as the kids say: next year I'll be starting an *exciting* new role at Shopify, continuing to work on web performance and the web platform, but with a particular focus on commerce. I can't wait to learn more about that space and its needs, and then bring those insights back to the web platform!!

As a result, Thursday will be my last day at Google. Working as part of Chrome's web platform team was a pleasure, an honor and a privilege

If you use unload handlers, then you should check out this potential change in Chrome.

Unload handlers are VERY unreliable but on desktop they also prevent the use of the bfcache on Chrome (and Firefox), while on mobile they don't. We want to align it to how it works on mobile.

https://groups.google.com/a/chromium.org/g/blink-dev/c/oU1yt5cdGH8

SPA view transitions land in Chrome 111

https://developer.chrome.com/en/blog/spa-view-transitions-land/

It seems New Relic will soon stop using an unload event listener. This prevented pages to benefit from the ultra-fast back/forward cache.

They shipped an experimental setting last month: https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1222/

And they're about to make it the default: https://github.com/newrelic/newrelic-browser-agent/pull/401

Yeah for faster websites!

We now have 3 LGTMs on view transitions, meaning it can start the journey to Chrome stable without a flag! https://groups.google.com/a/chromium.org/g/blink-dev/c/AJJiH6Pjr50?pli=1

If you want your sites to have transitions by the time this lands, now's the time to look into it 😀 https://developer.chrome.com/docs/web-platform/view-transitions/