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!
Energy efficiency seems harder to achieve in the short term, and relies on self restraint which the lack thereof got us where we are... Forcing further frugality by necessity might have an impact on demands for non essential goods. The energy aspect might see some improvements as a result of that (less goods to transport/create). That said, it's not clear how much margin that is vs. the war in Ukraine and how that gives pricing power to the gas suppliers.
Yoav Weiss
Barry Pollard
Chromium for Developers
Anthony
mytwobits01
Ricky Mondello