AnthonyFeb 13, 2023

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!

Browser agent v1222 | New Relic Documentation

Browser agent v1222

Show threadŠime VidasFeb 14, 2023

@anthony

> We target and test support for just the last ten versions of Chrome, Edge, Safari, and Firefox

The last ten versions of Safari?! What is that, 2012? 😆

Show threadAnthonyFeb 14, 2023
@simevidas What is a version ? Are 16.0, 16.1, 16.2 one or three versions?
Show threadŠime Vidas
@anthony If that’s the case, then last 10 versions goes only to 15.0. That would be a problem because a significant number of mobile requests are coming from Safari 14 and older (1.7% in total https://analytics.wikimedia.org/dashboards/browsers/#mobile-site-by-browser/browser-family-and-major-hierarchical-view)
Dashiki: Simple Request Breakdowns

Feb 14, 2023 at 4:25pmPinafore
Show threadAnthonyFeb 14, 2023

@simevidas Sorry my answer was missing an indicator of sarcasm.

I meant that New Relic's docs are not clear enough with that statement. And the linked pages are not helpful either.