Browser agent release notes

Browser agent v1228

Tue, 21 Mar 2023 00:00:00 +0000

Bug Fixes

Fix negative offset timings

Fix an issue that caused session trace offset timings to be miscalculated in the early-page lifecycle, sometimes leading to negative "backend" timings.

Browser agent v1.229.0

Fri, 31 Mar 2023 00:00:00 +0000

v1.229.0

Use semantic versioning scheme

The agent will now utilize semantic versioning for subsequent releases. The previous version (1228) will carry forward into 1.229.0, and so on.

Use `web-vitals` library for internal timing calculations

In an effort to align and standardize the timings the agent collects, the agent now uses the Google CWV library to track page timings such as CLS, LCP, FCP, TTFB and more. See Core Web Vitals documentation for more information.

Ship the Browser Agent repository to NPM

The Browser Agent repository will now be available as a pre-release NPM package. See @newrelic/browser-agent for more information.

Support statement:

New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.

New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.

Browser agent v1.230.0

Mon, 10 Apr 2023 00:00:00 +0000

v1.230.0

Add persistence for custom attributes

Custom attributes may now optionally be persisted between page loads via session storage. The API method setCustomAttribute now takes a third parameter, which defaults to false. When true, this boolean indicates that the provided custom attribute should be persisted in session storage and restored on subsequent page loads. Session storage is subject to the same-origin policy of the browser.

Add setUserId API

A new setUserId API method is now available. It defines a custom attribute containing a specified user ID, to be included in all payloads. The setUserId API is an extension of the setCustomAttribute API and automatically persists between page loads.

Fix npm package browser targets

The previous npm package release included code that was not compatible with browsers in our supported browser list. The package exports will now default to code that matches our browser support list. The package will also include the source code for power users that would like more control over how the agent is built.

Fix npm package exports

Some dangling, unused, and non-existent imports and exports were causing issues with consuming the NPM package in some projects. These have been removed.

Fix npm package import for typescript projects

Fixed an issue where typescript projects attempting to import the browser agent library would not get proper auto-complete in the import statement and would receive module declaration errors. The browser agent will not use tsc to generate type definitions from the JavaScript code at build time. The package.json has been updated with appropriate type export declarations.

Add error catch around sendBeacon

Added error catch logic around the sendBeacon usage. In the event sendBeacon throws an error during the final harvest, the final harvest will attempt to fall back to the image data submission method.

Remove array reduce polyfill

Removed the array reduce polyfill in favor of the native browser array reduce method.

Support statement:

Browser agent v1.231.0

Fri, 28 Apr 2023 00:00:00 +0000

v1.231.0

Omit CLS scores before web-vitals report them

Initial snapshots of CLS reported as 0s attached to timing metrics will be omitted, so as to "de-noise" the aggregate CLS dataset. This also temporarily addresses an edge case of long loading pages potentially sending a "final" CLS value of 0, inaccurately. The case of a final 0 CLS when a user only navigates away from the page has also been fixed.

Fix accepted argument type for `all` and `race` methods of `Promise`

The wrapped Promise's static all and race methods now work with iterators per native implementation, rather than only arrays.

Upgrade Navigation Timing API in `PageView` (RUM) call

The performance entry data sent for PageView now uses the Navigation Timing Level 2 API over the deprecated Level 1 API.

Fix typo in top-level API causing exception

An an uncaught reference exception was occurring on pages with more than one initialized agent due to a typo in the name of a variable (returnsVals).

Add null entry checks to certain web-vitals handlers

For LCP and FID, we will exclude the performance entry info when there are no entries given by web-vitals. This had thrown exceptions.

Remove previously added console logging measurements

This reverses performance impacts and exceptions introduced in the prior release by serializing console API arguments.

Rectify version reported by NPM agent implementations

Agents installed via the NPM method will report the correct semantic version in data harvests.

Fix exception when importing NPM package source code

An error was occurring related to a missing environment variable when importing from the NPM package source directly (versus via the CJS/ESM packages).

Support statement:

Consistent with our browser support policy, version v1.231.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 103-112, Edge 103-112, Safari 15-16, Firefox 103-112; and for mobile devices, Android Chrome 100 and iOS Safari 15-15.5.

Browser agent v1.232.0

Mon, 08 May 2023 00:00:00 +0000

v1.232.0

Features

Minor changes to SMs

Add internal metrics to track the duration of the average session, to improve estimation for future efforts.

Add query parameter supportability metrics

Adding supportability metrics to capture legacy network method usage, query parameter size statistics, and custom data size statistics.

Allow custom error grouping

The setErrorHandler method now supports applying custom fingerprints to exceptions. Events with the same fingerprint appear grouped together in the New Relic One errors inbox.

Add new stateful Session Manager

The agent will now manage the end-user session lifecycle statefully, across page views and tab changes.

Support statement:

We recommend you to upgrade the agent regularly so you get the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.

New Browser Agent releases are rolled out in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.

Consistent with our browser support policy, version v1.232.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-112, Safari 15-16, Firefox 103-112; and for mobile devices, Android Chrome 100 and iOS Safari 15-15.5.

Browser agent v1.232.1

Wed, 17 May 2023 00:00:00 +0000

v1.232.1

Bug Fixes

Add X-NewRelic-ID header only if defined

The agent will now set the X-NewRelic-ID header on XHR requests only when a truthy xpid value is explicitly set in the loader configuration. Previously the header was added even if undefined.

Identify inline stack trace URLs more precisely

URLs in JavaScriptError stack traces were sometimes misidentified as inline scripts when they shared a partial URL with the page on which the agent was loaded. The agent will now identify same-page scripts more precisely.

Support statement:

Consistent with our browser support policy, version v1.232.1 of the browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, Firefox 104-113. For mobile devices, v1.232.1 was built and tested for Android Chrome 100 and iOS Safari 15-15.5.

Browser agent v1.233.0

Fri, 26 May 2023 00:00:00 +0000

v1.233.0

Features

Capture metrics for usage of MooTools and certain polyfills

New supportability metrics have been added to capture MooTools library usage and presence of customer-defined polyfills for certain native JavaScript features, such as function binding and ES6 Array prototype methods.

Update agent internals in early preparation for new features

The agent code base now contains the non-functional foundations of session replay mechanics. Note that this code is dormant and disabled. It will not download or execute until the session replay feature and its downstream dependencies are in a finished state.

Bug Fixes

Address "configurable" warnings arising from user-agent module

The unused userAgent property and corresponding module have been removed from the runtime object due to "configurable" warnings being thrown in cases attempting to overwrite the runtime configuration.

Refactor usage of Array.from to address MooTools conflict

To work around a conflict with some versions of the MooTools library that mutate the native Array.from method, the agent will now use alternative methods.

Ensure runtime is preserved for late-configuration cases

Fix an issue where the internal runtime state of the agent was not preserved when the agent configurations were supplied after the loader had finished initializing, which caused the session to be cleared.

Support statement:

Consistent with our browser support policy, v1.233.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.233.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.233.1

Wed, 31 May 2023 00:00:00 +0000

v1.233.1

Bug Fixes

Address bug affecting XHR harvest re-schedule

A early return condition in the harvest rescheduling logic in version 1.233.0 was preventing Ajax event harvest from being rescheduled in cases where no data had accumulated.

Support statement:

Consistent with our browser support policy, v1.233.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.233.1 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.236.0

Tue, 27 Jun 2023 00:00:00 +0000

v1.236.0

Features

Expose MicroLoader in the npm package

The npm package now exposes an entry-point called MicroLoader, which may be used to instantiate multiple agents on one page. This loader type, which is smaller than the Lite loader, captures a distinct PageView event per instance but does not auto-instrument the page. Instead, manual API calls may be used to capture JavaScriptError and PageAction events via the noticeError and addPageAction methods.

Remove img, jsonp, and xhrGet methods

Unused agent network methods have been removed. All data transmitted by the agent will now default to using XMLHttpRequest POST calls except for data transmitted during a visibility change or page unload. Visibility changes and page unloads will use sendBeacon with a fallback to fetch with keepalive. For browsers that do not support sendBeacon, the final data transmission will use XMLHttpRequest POST.

Bug Fixes

Handle chunk load promise error introduced in 1.235.0

Starting in 1.235.0, loading the agent in browsers with strict privacy settings resulted in an uncaught error in a promise. This error has been handled, and chunk load failures again result only in a warning.

Fix illegal invocation error on final harvest

An issue from 1.234.0 has been addressed in which an illegal invocation error could occur during a final harvest as a result of calling addPageAction and passing window.location as an argument before a navigation.

Support statement:

Consistent with our browser support policy, v1.236.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 105-114, Edge 105-113, Safari 15-16, and Firefox 105-113. For mobile devices, v1.236.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.237.0

Fri, 28 Jul 2023 00:00:00 +0000

v1.237.0

Features

Stop reporting ajax events going to same beacon

Network requests made to the same hostname as the agent's reporting beacon endpoint are no longer captured, by default. As an example, outgoing XHRs to the bam.nr-data.net URL where analytic data is typically sent would not reflectively record itself.

Add warning for large payloads

Add warning for large payloads, which is typically caused by excessive custom attribute sizes.

reduce jserrors wrapping and remove onerror use

Replaces the use of the onerror global function with addEventListener to capture errors that go unhandled by customer code. This does not change how unhandled promise rejects are captured. Additional wrappings for events, timers, and animation fames have been removed in favor of capturing unhandled errors using a global event listener.

Bug Fixes

Remove fetch keep-alive unhandled rejection

Eliminate an unhandled promise rejection error caused by fetch failure in agent EoL logic.

prevent invalid error stack traces

Removing the instantiation of the Error class in the jserrors feature for instances where a non-Error value is thrown from customer's code. In such cases, an Error instance would be created and the stack trace would point back to the agent code as the source. This causes confusion since it makes it seem like the agent code is throwing the error when that is not the case. Instead, the internal UncaughtError class will be used and no stack trace will exist.

Defining agent api methods for ts types

Updating the type interface of the Agent and MicroAgent classes to properly expose the agent API methods in the generated typescript types.

Fix potential property of undefined errors

Patch a couple of areas that can yield reading property of undefined or null errors in the RUM call and jsonp wrapper.

Support statement:

Consistent with our browser support policy, v1.237.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 106-114, Edge 105-113, Safari 15-16, and Firefox 106-113. For mobile devices, v1.237.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.235.0

Tue, 20 Jun 2023 00:00:00 +0000

v1.235.0

Features

Add error mode to session trace

Session-enabled traces now have an "error mode" capability in which the feature lies dormant until an exception is thrown. Upon the error, the past 30 seconds of data is retained and sent, and the feature becomes fully activated again.

Minor feature class changes to support testing new features

Feature class internals and testing architecture have been augmented to support testing new experimental features in progress.

Decorate error objects to facilitate future UI experiences

Error payloads will now be decorated with a real timestamp and feature flags to facilitate error usages in future NR1 UI experiences.

Use new shared session for Session Trace feature

Session Trace becomes more aligned with the new interpretation of a user's session defined as part of the upcoming and experimental Session Replay feature. When the session tracking setting is enabled, the Session Trace feature will now use stored session info to make capturing decisions.

Remove unused data from session trace requests

Data defined by APM agents and the customer will no longer be included in session trace requests since the data is not consumed downstream and can result in 414 errors in cases where the custom data would cause the URL to exceed the maximum length of 8,192 bytes.

Support statement:

Consistent with our browser support policy, v1.235.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 105-114, Edge 105-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.235.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.234.0

Fri, 02 Jun 2023 00:00:00 +0000

v1.234.0

Features

Migrate RUM network call from GET to POST

When making its initial network call (the RUM call), the agent will now use the POST method instead of the GET method and will not depend on JSON-P to trigger follow-on events. This change facilitates setting custom attributes in the request body, reducing the likelihood of long GET URLs.

Support statement:

Consistent with our browser support policy, v1.234.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-114, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.234.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.

Browser agent v1.237.1

Wed, 02 Aug 2023 00:00:00 +0000

v1.237.1

Bug Fixes

SPA feature respects ajax deny_list for fetch

The SPA feature will now properly respect the Ajax deny list and block internal settings for fetch calls. In prior versions, the SPA feature only consulted the Ajax deny list for XMLHttpRequest calls.

prevent dollar symbol only variable names

Prevent the build process of the agent from creating minified variable names that only contain the dollar symbol. If such a variable is immediately followed by an ampersand, as could be the case in a minified logic block, it could be picked up by string replacement logic applied to outgoing HTML within their server.

Undefined deny list ignores block internal

In cases where the customer's configuration does not include the init.ajax.deny_list property, the agent would not properly account for the init.ajax.block_internal setting and would not block Ajax events for internal agent network calls.

Fix serialization issue with array data

Update the harvester to account for array payloads, which in niche cases could convert array payloads to indexed objects.

Support statement

Browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.

Consistent with our browser support policy, v1.237.1 of the browser agent was built for and tested against these browsers and version ranges:

Chrome 106-114
Edge 106-113
Safari 15-16
Firefox 106-113.

For mobile devices, v1.237.1 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.

Browser agent v1.238.0

Wed, 16 Aug 2023 00:00:00 +0000

v1.238.0

Features

Reducing the agent chunk count

Reducing the number JavaScript files the agent loads asynchronously down to a single file. This means customer's users will now only need to load one additional JavaScript file for the New Relic Browser Agent to operate. This additional JavaScript file will continue to only be loaded upon the document "load" event. This change not only reduces the number of additional requests the agent must make but also reduces the amount of code that must be loaded by eliminating duplication.

Add API: setApplicationVersion

Add api method to top-level interface to allow the setting of application version across all outgoing payloads

Bug Fixes

Capture potential missing tail data for session trace

Send buffered session trace data in certain cases when it's being discarded at the tail end of a captured session.

Fix distributed tracing handling of empty string fetch parameter

Fixing an issue with distributed tracing that would result in an exception within the agent when fetch is called with an empty string as the first parameter.

Typo in type declarations

Fixing typos made in the browser and micro agent API declarations. This includes adding internal test cases for those types to ensure this issue does not happen again.

Support statement:

Consistent with our browser support policy, v1.238.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 106-114, Edge 106-113, Safari 15-16, and Firefox 107-113. For mobile devices, v1.238.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.

Browser agent v1.239.1

Fri, 01 Sep 2023 00:00:00 +0000

v1.239.1

Features

Add best effort to detect Ajax events before instantiation

Add a "best effort" at detecting ajax events that may have happened on the page before the agent was instantiated by utilizing the ResourceTiming browser API.

Add mode to enable agent to not harvest until user consent

Add ability for customers to wait to start harvesting. This behavior will utilize a configuration setting in tandem with an API call to trigger features to begin harvesting.

Remove allow_bfcache flag

Removes unused code which still relied on the window unload event. Going forward, the only method the agent will use to monitor potential end of page session will be visibility change in accordance with modern web practice.

Remove old supportability metrics

Removing supportability metrics that are no longer needed including polyfill detection, bfcache usage, body and query bytes sent count, and custom attributes size.

Bug Fixes

Fix issue with leaking event listeners

Fixing an issue where session timeout would result in rewrapping global event handlers. For instances where the site would be open for long periods of time, such as kiosks, this would eventually result in a degradation in event handler performance.

Issues with types resolution

Fixing issues with typescript throwing errors when trying to resolve the typings for individual features with "moduleResolution": "node" set in the tsconfig.json. "moduleResolution": "nodenext" and "moduleResolution": "node16" will enable typescript use of the exports field of our package.json but could also break other libraries and forces developers to change all local imports to include file extensions.

Support statement:

Consistent with our browser support policy, v1.239.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.238.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.

Browser agent v1.240.0

Tue, 12 Sep 2023 00:00:00 +0000

v1.240.0

Features

Origin of agent webpack chunks now changeable

Allow the agent to operate through a proxy. The agent needs to be able to fetch its source code and send analytics to a different domain, and this solves the former. NPM is not affected.

Add session trace metadata params

Add first timestamp and node count information to session trace payloads for optimization in UI experiences.

Add SR to pro and spa builds (only runs for LP customers)

Add the SR feature to Pro and Pro+Spa builds of the agent. The session replay library shipping with this version of the browser agent is in limited preview and is not turned on by default. To use the feature, users will need to be part of the limited preview customer group and configure their browser application settings in the UI.

Centralize web vitals timings

Centralize web vitals timings to be accessible from any part of the agent.

Support statement:

Consistent with our browser support policy, v1.240.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.240.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.

Browser agent v1.242.0

Mon, 25 Sep 2023 00:00:00 +0000

v1.242.0

Features

Add messaging about Session Replay abort behavior

Add messaging to signal why a replay aborted, which could happen for a number of reasons.

Applying new cache headers to assets

Released browser agent assets will now be delivered with a 1 year cache header. This will allow user's browsers to cache the async chunks the agent loads for much longer and eliminate performance recommendations found in synthetic performance tools like Lighthouse. This will be applied retroactively to all released versions of the agent.

Bug Fixes

Drain event emitter even when feature fails to initialize

A failure to import and initialize a feature could block the agent from draining data out of the event emitter, which prevents the agent from making any successful calls. This fix allows the event emitter to drain even when an individual feature fails to initialize.

Validation of SR configurations

Update the block selector, mask selector, and mask input setters to handle empty strings.

Support statement:

Consistent with our browser support policy, v1.242.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.242.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.

Browser agent v1.243.1

Wed, 04 Oct 2023 00:00:00 +0000

v1.243.1

Bug fixes

Improve Session Replay abort metric reliability

Pass Session Replay abort metrics through the event emitter buffer to guarantee that early lifecycle failures are captured by the Metrics feature for prioritizing future improvements.

Support statement:

Consistent with our browser support policy, v1.243.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.243.1 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.

Browser agent v1.241.0

Mon, 18 Sep 2023 00:00:00 +0000

v1.241.0

Features

Add SR entrypoint to NPM ahead of LP

Add SR instrumentation entrypoint to NPM ahead of the upcoming Limited Preview window

Removing hash from chunk asset name

Removing the hash from the chunk asset file name. This will allow internal and external automation to predict the file name of each asset chunk as long as the loader type and version number is known.

Bug Fixes

Final harvest does not happen when initial RUM call fails

Fixes the final harvest behavior in cases when the RUM request fails. The initial request is meant to act as a gateway for the agent to start reporting data, and its failure should result in the agent not sending anything. As of previous version, the metrics and page view timing features do not follow this rule, and that has been corrected.

Support statement:

Consistent with our browser support policy, v1.241.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.241.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.

Browser agent v1.243.0

Wed, 04 Oct 2023 00:00:00 +0000

v1.243.0

Features

Do not report ajax nodes in session traces if in deny list

Prevent ajax nodes derived from calls found in the ajax deny list from populating Session Trace payloads

Remove deprecated API inlineHit

Removing the browser agent API inlineHit. This API was deprecated in 2014 and is no longer supported or used by newer versions of the browser agent.

Bug fixes

Re-update assets proxy to accept host URL strings

Previously, the agent expected the protocol (for example, https://) to be included in the configuration input. However, we have since decided to allow the protocol to be excluded, as the proxy beacon field only accepts a host string.

Adjust Session Replay meta and timestamps

Ensure that payloads can not ends with a meta node or start with a snapshot node for consistency in UI render queries.

Tap session entity into storage API for changes across tabs

Tap session entity into storage event listener for stateful changes across tabs.

Set Session Replay first chunk flags more reliably

Add logic to set firstChunk flag and replay mode on new replays more reliably.

Support statement:

Consistent with our browser support policy, v1.243.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.243.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.

Browser agent v1.244.0

Tue, 10 Oct 2023 00:00:00 +0000

v1.244.0

Features

Bump rrweb to 2.0.0.11 and make constant dynamic at build time

Bump rrweb dependency version to 2.0.0.11 and include in Session Replay payload metadata dynamically

Add Session Replay configurations to collect inline assets

Add Session Replay configurations to collect inline images, stylesheets, and fonts for private applications.

Ensure 15 second minimum error buffer when possible

Add a two-step sliding window to ensure 15-30 second buffer time for applicable error replays

Bug fixes

Fix invalid timestamps

Ensure that Session Replay node injection does not cause desynchronized timestamps for blob payloads

Isolate browser interaction node

Improving context isolation for events the SPA feature tracks to allow for multiple agent bundles to live on the same page. This is only intended for internal New Relic usage at this time and should not affect customers.

Support statement:

Consistent with our browser support policy, v1.244.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.244.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.

Browser agent v1.246.0

Mon, 23 Oct 2023 00:00:00 +0000

v1.246.0

Features

Replace url parsing with URL class

Replacing internal url parsing logic with the browser built-in URL class.

Add network info to all page view timing events

Add client network information to all PageViewTiming events in New Relic. The attributes currently only exist on LCP and FI event types and will now be reported with all others such as load and pagehide events.

Bug fixes

Add feature flag support for Browser Interactions

Implementing a feature flag that will disable the fix 315. That fix was specifically around Angular, React, and Vue applications with routes containing network calls resulting in browser interactions missing those ajax calls. This feature flag should not be enabled unless specifically instructed to do so by support.

Add first harvest of session flags to RUM and Trace

Mark the first RUM call and Session Trace harvest of any given session so that it becomes queryable in New Relic.

Support statement:

Consistent with our browser support policy, v1.246.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-118, Edge 109-117, Safari 15-16, and Firefox 109-118. For mobile devices, v1.246.0 was built and tested for Android Chrome 100-118 and iOS Safari 15.5-16.2.

Browser agent v1.245.0

Wed, 18 Oct 2023 00:00:00 +0000

v1.245.0

Features

Allow boolean values in setCustomAttribute

Allow boolean values to be supplied to newrelic.setCustomAttribute() API calls.

Detect GraphQL operation names and types in AJAX calls

Detect GraphQL operation names and types in AJAX calls and decorate AJAX events with that information.

Removing worker build

Removing the worker build from the agent. The worker build was a never released custom build of the agent that could be imported into web and service workers. The agent will continue to support running in those contexts but customers will need to use the NPM package to create their own customized agent for those contexts.

Support statement:

Consistent with our browser support policy, v1.245.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 109-118. For mobile devices, v1.245.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.

Browser agent v1.246.1

Tue, 31 Oct 2023 00:00:00 +0000

v1.246.1

Bug fixes

Fix missing type declarations

Fixing missing type declarations in the feature utilities that show up when skibLibCheck is not enabled in the tsconfig.

Support statement:

Consistent with our browser support policy, v1.246.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-118, Edge 109-117, Safari 15-16, and Firefox 109-118. For mobile devices, v1.246.1 was built and tested for Android Chrome 100-118 and iOS Safari 15.5-16.2.

Browser agent v1.248.0

Thu, 16 Nov 2023 00:00:00 +0000

v1.248.0

Features

Report enduser.id with Session Replay

Report enduser.id if set with Session Replay data to improve faceting the Session Replay UX

Bug fixes

Fix issue with errors forcefully triggering session traces

Fixing an issue where an uncaught error or calls to the noticeError API would force session trace to begin collecting and harvesting data, even though session trace and session replay were disabled via the RUM response.

Support statement:

Consistent with our browser support policy, v1.248.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 110-119, Edge 110-118, Safari 15-16, and Firefox 110-119. For mobile devices, v1.248.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.

Browser agent v1.247.0

Tue, 14 Nov 2023 00:00:00 +0000

v1.247.0

Features

Session Replay API

Add two new APIs for controlling session replay behaviors:

newrelic.recordReplay()
newrelic.pauseReplay()

Add relative timestamps to Session Replay payloads

Add relative timestamps to Session Replay payloads to allow for server-side clock skew adjustments and improve the API pagination experience.

Expose library versions used to capture session replay data

Expose library versions used to capture session replay data, which helps sync visualizations in the UI Replayer components across version migrations.

Add basic support for deferring the browser agent loader script

Add basic support for deferring the browser agent loader script, including exposing a DOM-level event for external use to indicate the agent is successfully running.

Enable SRI and nonce attributes for async chunks

Additional JavaScript resources loaded by the agent will now include a SHA512 integrity hash and will respect the presence of a nonce token on scripts loaded on the page. This gets the agent closer to being able to run within an environment with a more secure content security policy.

Add session durationMs to Session Replay payloads

Add current session's running duration to all outgoing session replay payloads for use with ingest estimations

Support statement:

Consistent with our browser support policy, v1.247.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-119, Edge 109-118, Safari 15-16, and Firefox 109-119. For mobile devices, v1.247.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.

Browser agent v1.249.0

Thu, 14 Dec 2023 00:00:00 +0000

v1.249.0

Features

Allow empty string for session replay masking value

Allow empty strings to be provided for session replay masking values, which helps the UI/API provide sane fallbacks for never-set values.

Bug fixes

loader missing sub-resource integrity hashes

Sub-resource integrity hashes were not being properly generated and included in the loader for async chunks related to session replay. This would cause a warning to appear in the browser console, but would not block those chunks from loading. This would have only affected customers taking part in the session replay limited preview.

Fix API warning messages

Fix warning messages given by API calls made before the agent has initialized.

Traceids not random when using `webcrypto`

Fix non-random hexadecimal generation when using the webcrypto api, which in turn creates non-random traceIds, that always end in 00.

Support statement:

New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. We no longer support older releases when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.

New Browser Agent releases roll out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.

Consistent with our browser support policy, v1.249.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 110-119, Edge 110-118, Safari 15-16, and Firefox 110-119. For mobile devices, v1.249.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.

Browser agent v1.250.0

Tue, 09 Jan 2024 00:00:00 +0000

v1.250.0

Features

Add a flag to note that a payload occurred during a replay

Added a flag to mark harvests as having occurred during an active session replay. This will aid cross-feature querying in NR1.

Session Replay Dynamic Loading

Allow Session Replay modules to load earlier in the page lifecycle if a replay is ongoing

Bug fixes

TraceId generation regression (non-random trace ids)

Fixes a regression which caused all trace ids generated to end in a 0.

Support statement:

Consistent with our browser support policy, v1.250.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-119, Edge 111-118, Safari 16-17, and Firefox 111-119. For mobile devices, v1.250.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.

Browser agent v1.251.0

Wed, 24 Jan 2024 00:00:00 +0000

v1.251.0

Features

Session Replay - Detect Non-Inlined Stylesheets

Add check for invalid stylesheet inlining and asynchronously fetch the stylesheet contents for future payloads.

Bug fixes

Bubble Up API Methods to Top-Level Instance For NPM

Fix an issue where the NPM wrapping of the agent would not bubble the APIs up to the top-level of the instance, causing invalid warnings to log.

Add fallback for currentBufferTarget

Add a fallback to the currentBufferTarget for cases where the preload buffer has been cleared

Support statement:

Consistent with our browser support policy, v1.251.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-120, Edge 111-119, Safari 16-17, and Firefox 112-120. For mobile devices, v1.251.0 was built and tested for Android Chrome 100-120 and iOS Safari 15.5-16.2.

Browser agent v1.251.1

Mon, 29 Jan 2024 00:00:00 +0000

v1.251.1

Bug fixes

Pass unload options to simultaneous harvests in session replay

Pass unload options to simultaneous harvests in session replay to allow all calls to utilize sendBeacon when unloading.

Fix deferred session replay payloads

Force agent to send preloaded session replay payloads if present at load time.

Support statement

New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.

Consistent with our browser support policy, v1.251.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-120, Edge 111-120, Safari 16-17, and Firefox 112-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-120 and iOS Safari 15.5-16.2.

Browser agent v1.252.0

Mon, 12 Feb 2024 00:00:00 +0000

v1.252.0

Features

Add types mappings for esm distribution

Adding typescript types mappings for the ESM distribution in the npm package.

Report config changes away from default state for UX improvement

Detect if the default config values have been altered at runtime. This is useful to evaluate what the reasonable defaults are across a customer base over time to provide a better UX.

Create more granular metrics about stylesheet fix success

Utilize a finer granularity when collecting success metrics on local stylesheet fixes for Session Replay compatibility.

Align browser reported uncaught syntax errors

Aligning the data reported for uncaught syntax errors across modern browsers. Chrome specifically fails to include the file name and line number in instances of SyntaxError. This could also cause issue in the New Relic error inbox where Chrome syntax errors were not being properly grouped.

Capture Internal Metrics for Session Replay Configurations

Capture supportability metrics sounding Session Replay configuration usage to improve user experiences around configuration of the agent's Session Replay feature.

Bug fixes

Add safe logic to snapshots

Safe-guarded a race condition where an asynchronous call to fix a stylesheet could trigger the agent to try to force a snapshot after it has already stopped recording due to a visibility change.

Fix adblock memory leak

Fixed memory leaks caused by request resolve failure (e.G. due to adblocker). Thanks to community member @Joe-Degler for contributing this fix.

Support statement

Consistent with our browser support policy, v1.252.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-120, Safari 16-17, and Firefox 113-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.

Browser agent v1.252.1

Thu, 29 Feb 2024 00:00:00 +0000

v1.252.1

Bug fixes

Fix webpack imports in npm package

Fixing some import overrides in our NPM package build to prevent imports existing that include code reliant on webpack globals. This will resolve the error Uncaught ReferenceError: __webpack_require__ is not defined when using the NPM package in a project that does not use webpack.

Page load after session timeouts don't start new session

When a session expires or becomes inactive while the user does not have the page open and they re-open the page, that is now treated as a new session.

Support statement

Consistent with our browser support policy, v1.252.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-121, Safari 16-17, and Firefox 113-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.

Browser agent v1.254.0

Mon, 25 Mar 2024 00:00:00 +0000

v1.254.0

Features

Standardize all feature behavior to wait for RUM response

Force features to wait for entitlement checks from the rum call before processing buffered data.

maintain a harvestCount for use later with harvestId

Add a counter which increments after every harvest. This will be used in a future effort to curate a unique harvest ID for API paging purposes.

Add rum-response metadata handler

The initial connect call can now supply browser app metadata. This adds a handler to store and use that metadata for future harvests.

Calculate New Relic time in the agent

Migrating the process of time-stamping harvested data to the agent. The agent uses the date and time reported by the ingest pipeline during the RUM call as well as browser network and timing stats to derive a server time offset that can be applied to harvested data as event occur. This improves the ability to visualize the harvested data on a timeline within the New Relic UI.

Bug fixes

Remove webpack imports in npm package

Transitioning certain module imports so that the default import is for the npm version of the module instead of the cdn or webpack version. This should completely eliminate all references to webpack globals when using the npm package.

Support statement

Consistent with our browser support policy, v1.254.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.

Browser agent v1.254.1

Tue, 26 Mar 2024 00:00:00 +0000

v1.254.1

Bug fixes

Server Timing - Remove reliance on performance API

Removing reliance on the browser resources API for the calculation of New Relic server time. On site with many resource requests, there was a small chance that the RUM network call would be flushed from the resources API cache before we could capture it and calculate server time.

Support statement

Consistent with our browser support policy, v1.254.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.253.0

Wed, 13 Mar 2024 00:00:00 +0000

v1.253.0

Features

Soft Navigations trial

Introducing a lighter and simplified version of the existing spa feature that tracks soft navigations. This new feature still sends BrowserInteraction events, but the duration and finishing of those interactions have been redefined. As a replacement, it ought to reduce complexity and integration issues around the existing spa and exhibit better and faster performance.

Apply deny list to ajax metrics

The ajax deny list has historically only applied to the collection of ajax events and not ajax metrics. With this feature, the deny list will also be applied to the collection and reporting of ajax timeslice metric data. If an ajax request matches an entry in the deny list, both events and metrics will be blocked from being collected in the agent. This feature will be behind a feature flag to assess impact before final complete rollout. Thanks to community member @Wrhector for contributing this feature.

Preload the session replay recorder when properly configured

Load the session replay recorder module before the page load when configured to do so. This will increase visibility for recordable data for customers who have opted in to the behavior.

Isolate observation context per agent

Initial implementation of an isolated observation context per agent running on the same page. This reduces the modification of instances of globals like events and instead each agent will track its own observation context internally.

Support statement

Consistent with our browser support policy, v1.253.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.

Browser agent v1.255.0

Thu, 04 Apr 2024 00:00:00 +0000

v1.255.0

Features

Adjust session replay timestamps to New Relic server time

Adjust all timestamps sent as session replay event nodes to represent New Relic server time for accuracy in querying against adjacent but separate events in the timeline such as errors, page views, and interactions.

Send CLS as timing node additionally

cumulativeLayoutShift can now be queried for (with that as its timingName) as its own PageViewTiming event in New Relic. The additional attribution are a part of these events, and the values are more reflective of true end-session CLS scores.

Update agent to use new relic server time

Update the agent to use New Relic server time as the timestamp for harvested page action and error data.

Switch web vitals library to attribution build

Report extra attributes for each vital using web vital library's attribution build.

Support statement

Consistent with our browser support policy, v1.255.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.256.0

Thu, 11 Apr 2024 00:00:00 +0000

v1.256.0

Features

Generate PTID in Agent

Generate PTID in agent instead of in RUM response. This allows PageView events to be decorated with a page trace ID.

Allow unmasking elements with nr-unmask selectors

Add custom masking mechanism to allow unmasking elements with nr-unmask class selectors and data-nr-unmask data attribute selectors

Adjust Session Replay Error Tracking

Adjust when errors are decorated with session replay identifiers to more closely match actual recording data

Bug fixes

stabilize timestamp corrections

Ensure Session Replay timestamps are only ever adjusted once and fix correction factor to alleviate timeOrigin inconsistencies

Resume Page Focus Now Checks Session State

Check session state when resuming focus to an actively instrumented page. This ensures that stale sessions are caught before invoking other feature-level methods.

Support statement

Consistent with our browser support policy, v1.256.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.257.0

Thu, 18 Apr 2024 00:00:00 +0000

v1.257.0

Features

Session Replay preload optimizations

Optimize early load error detection to mitigate certain race conditions when transitioning from error mode to full mode.

Decorate errors with hasReplay individually

Change the error aggregation method to consider errors with a hasReplay flag separately to ensure timestamps are always correct. Decorate each aggregation set with hasReplay directly instead of a request-level query param

Bug fixes

Session replay preload without autoStart

In scenarios where SessionReplay was configured to not auto start and the user already has a replay recording from a previous page or after a page reload, calls to the start('session_replay') API made too soon after agent initialization would be ignored.

JSEerrors harvest hasReplay decoration

In scenarios where the SessionReplay feature was preloaded but a recording was never started, errors happening on the page would be improperly decorated with the hasReplay flag.

Agent class type declarations

Fixing incorrect type declarations for the constructor parameters of the Agent class.

Soft navigations memory leak on harvest

Address a couple scenarios of memory being not released by the soft navigation harvest cycle.

Support statement

Consistent with our browser support policy, v1.257.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.256.1

Mon, 15 Apr 2024 00:00:00 +0000

v1.256.1

Bug fixes

Revert "Generate PTID in Agent"

Revert a change causing Trace to begin harvest even when the rum flag given is 0.

Support statement

Consistent with our browser support policy, v1.256.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.258.0

Mon, 29 Apr 2024 00:00:00 +0000

v1.258.0

Features

Restructure AJAX Aggregate

Re-organization of the Ajax feature as part of agent maintenance. This has no expected impact on its functionality.

Maintain calculated NR server time for session

This update changes the agent to store the New Relic server time calculated when session tracking is enabled. This will prevent the agent from re-calculating server time on subsequent page loads, ensuring the timeline view of events in New Relic is more accurate.

Add harvestId to Session Replay payloads

Adds a unique harvest ID to Session Replay payloads to support better indexing and querying on the platform.

JSErrors timestamped per harvest

JSErrors that happen multiple times throughout a page's life will now receive a timestamp unique to the agent harvest cycle instead of consistently reporting the timestamp of the first occurrence of that error.

Bug fixes

Clean up xhrWrappable

Remove xhrWrappable which is an old variable checking for addEventListener on XHR. It is expected to have no compatibility impact on modern standard frameworks or browsers.

Prevent null CLS

Add a check to prevent null and undefined web-vitals values from being reported.

Support statement

New Relic recommends upgrading the agent regularly to ensure you get the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.

Consistent with our browser support policy, v1.258.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-123, Edge 114-123, Safari 16-17, and Firefox 116-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.

Browser agent v1.258.1

Tue, 07 May 2024 00:00:00 +0000

v1.258.1

Bug fixes

Improve Error Casting

Improve detection of line and column to allow errors that throw without a stack -- such as some chrome errors -- to still get basic error location information

Run inside cross-origin iframes for firefox/safari

Resolve a bug that prevented the agent from running in cross-origin iFrames for Firefox and Safari due to how the browsers implement context security.

Exclude data url requests as captured AJAX events

Do not report XMLHttpRequest or fetch calls made for data urls. The event and metric created for data urls are sparse and unhelpful, so they are no longer being captured or sent.

Session trace nodes de-duplication

Remove duplicated error and event nodes in traces. Each error noticed by the JS errors feature will now only be 1 node instead of 3. Each occurrence of any event fired on for a DOM node or XMLHttpRequest object is pared down to 1 instead of being directly proportional to the number of subscribed listeners.

Remove API start()'s features param

The start() method in agent API no longer accepts an argument. It will forcibly start all features that were marked autoStart: false in the configuration that has not yet started when it is called. If page_view_event had this property set to false, the agent will not send anything until start is called.

Support statement

Consistent with our browser support policy, v1.258.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.

Browser agent v1.258.2

Tue, 07 May 2024 00:00:00 +0000

v1.258.2

Bug fixes

Prevent noticeError() API from running if not given an argument

Short circuit the execution of the noticeError API if an argument is not supplied

Support statement

Consistent with our browser support policy, v1.258.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.

Browser agent v1.260.0

Mon, 13 May 2024 00:00:00 +0000

v1.260.0

Features

Improve time stamping of page view events

Improved the time stamping of page view events for subsequent page loads when sessions are enabled. Subsequent page loads will use the calculated New Relic server time to make the timestamp more accurate.

Bug fixes

Adjust session entity to not race between tabs

Allow individual tabs loading simultaneously to calculate New Relic server time.

Add internal error handler to session replay recorder

Fixed a bug where internal errors caused by the internal session replay recording library from being reported as customer errors. They now report as internal errors.

Support statement

Consistent with our browser support policy, v1.260.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.

Browser agent v1.260.1

Thu, 16 May 2024 00:00:00 +0000

v1.260.1

Bug fixes

Undefined stns in blob Trace

Fix an instance of undefined error in Session Trace feature introduced in v1.259.0. Harvest will now no longer be attempted if there are no trace nodes to send.

Support statement

Consistent with our browser support policy, v1.260.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.

Browser agent v1.259.0

Wed, 08 May 2024 00:00:00 +0000

v1.259.0

Features

Migrate Session Traces to Use Blob Consumer with Feature Flags

Create migration path for Session Traces to use the Blob Consumer, which aligns Session Traces and Session Replays and allows for better ingest scaling.

Support statement

Consistent with our browser support policy, v1.259.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.

Browser agent v1.261.0

Tue, 25 Jun 2024 00:00:00 +0000

v1.261.0

Features

Pass logging API args as object for better extensibility

Pass logging API arguments an object to allow for better extensibility later without requiring so many arguments for options.

Logging feature harvesting and optimizations

Allow the new logging feature to process and send harvests while optimizing log capture mechanisms

Create logging feature

Add basis of logging feature for handling and buffering observed log data

Add Logging Configurations

Add default configuration settings to be used for upcoming logging feature

Add wrapLogger API method for wrapping 3rd party loggers

Observe existing logging functions and report through event emitter for later processing when capturing log events.

Add Logging API entry points and central handler

Add Logging API interface and central handling mechanism as customer interface for capturing logging data

Bug fixes

Reading finish of null in SPA

Patch cases wherein SPA .end() can throw exception on a finished or full interaction. .end still force finishes an interaction.

dedup pre-load ajax requests

Fixing an issue where ajax requests made prior to the page load event would be reported as part of the SPA data and as standard ajax events.

Prevent session reset triggers from harvesting session trace data

Prevent Session Traces from "final" harvesting if the session identifiers change during a page life-cycle, such as when a session becomes stale and resets.

Support statement

Consistent with our browser support policy, v1.261.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-125, Edge 116-126, Safari 16-17, and Firefox 116-126. For mobile devices, v1.261.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.

Browser agent v1.261.1

Wed, 26 Jun 2024 00:00:00 +0000

v1.261.1

Bug fixes

Unhandled promise rejection for session import

Fixing an issue where an unhandled promise rejection could be thrown from the agent when using the npm package if the session manager async chunk get blocked or fails to setup a session.

Support statement

Consistent with our browser support policy, v1.261.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-125, Edge 116-126, Safari 16-17, and Firefox 116-126. For mobile devices, v1.261.1 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.

Browser agent v1.261.2

Mon, 01 Jul 2024 00:00:00 +0000

v1.261.2

Bug fixes

recordReplay will restart replays on same session page loads

Patch a case of recordReplay not restarting session replay. Customers can now programatically continue the session replay after a hard page navigation.

Support statement

Consistent with our browser support policy, v1.261.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.261.2 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.

Browser agent v1.262.0

Tue, 09 Jul 2024 00:00:00 +0000

v1.262.0

Features

logging bundle optimization

Improve the bundle size of the logging feature by moving non-critical pieces to the aggregation portion of the agent code.

Bug fixes

Release backlog memory when features are blocked by RUM

Plug a memory leak in Session Trace and other features. When entitlement or enable flag from RUM request returns a 0 for a feature, the agent will now release the reference to the events buffer under that feature so it can be garbage collected.

address call to stopTimer on undefined scheduler

Fixed an issue where session trace stopping on one tab while the same site was opening in another tab could result in the second tab throwing an exception when attempting to call stopTimer() on an undefined harvest scheduler.

safeguard api calls

Adding a safeguard to prevent an exception from being thrown when browser agent APIs are called before the agent is fully initialized.

Support statement

Consistent with our browser support policy, v1.262.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.262.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.

Browser agent v1.264.0

Tue, 06 Aug 2024 00:00:00 +0000

v1.264.0

Features

Create generic events feature with 1,000 event limit

Create a feature that will normalize, aggregate and harvest all generic events.

Report Page Actions with Generic Events Feature

Report all customer PageAction data utilizing the new Generic Events feature.

Support statement

Consistent with our browser support policy, v1.264.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.264.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.

Browser agent v1.266.0

Mon, 16 Sep 2024 00:00:00 +0000

v1.266.0

Features

Removing long task

Previously, an agent configuration turned on reporting of long tasks that took over 50ms. This functionality is being shelved effective this agent version. The configuration will no longer do anything.

Bug fixes

Remove nullish coalescing inside getter

Removed a nullish coalescing assignment in a class getter -- which even though is claimed to be supported -- behaved badly in old versions of webkit browsers like Safari 15, some versions of Mobile Safari, and old chromium iOS browsers that use webkit.

Support statement

Consistent with our browser support policy, v1.266.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.266.0 was built and tested for Android OS 14 and iOS Safari 16-18.

Browser agent v1.263.0

Thu, 25 Jul 2024 00:00:00 +0000

v1.263.0

Features

Optimize bundle size with warning codes

Decrease bundle size by converting static strings to warning codes with an accompanying link to a web resource.

Shut down agent if improperly configured

Shut down initialization of the agent if improperly configured. Agents must be provided a valid licenseKey and applicationID at runtime.

Bug Fixes

Prevent agent using invalid date header

Shut down the agent when unable to read a correctly formatted date header for the page view event harvest. This prevents harvesting data with wildly inaccurate timestamps. This should only happen with third-party or non-agent code has tampered with the ajax response headers.

Support statement

Consistent with our browser support policy, v1.263.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.263.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.

Browser agent v1.265.1

Fri, 06 Sep 2024 00:00:00 +0000

v1.265.1

Bug fixes

Disable websocket wrapping

Fix websocket problems and breakage in application using other third party libraries dealing with sockets by removing the wrapping introduced in version 1.265.0.

Support statement

Consistent with our browser support policy, v1.265.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 117-127, Edge 117-127, Safari 16-17, and Firefox 118-128. For mobile devices, v1.265.1 was built and tested for Android OS 14 and iOS Safari 16-18.

Browser agent v1.265.0

Fri, 30 Aug 2024 00:00:00 +0000

v1.265.0

Features

Standardized feature buffering behavior

We've established one pattern for holding data before harvests and for retry logic that can be shared by the all of the features. This reduces bespoke logic per feature and establishes a pattern for use with future architecture changes.

Add `WebSocket` wrapper and supportability metrics

We added a wrapper to detect usage of WebSockets. This is intended to help evaluate viability of the agent tracking WebSocket data and its overall mechanism usage patterns.

Configure session replay to wait for `DOMContentLoaded`

We decreased the time spent waiting by triggering the session replay mutation observer wrapping on the DOMContentLoaded event instead of the previously used window load event. This ensures wrapping is completed before the load chain.

Removed internal barrel exports

We reduced the loader bundle size by reworking the internal source code imports and exports.

Added payload size evaluation to generic events feature

We've changed data harvesting, where now harvesting occurs early when the payload reaches 64kb and and will harvests from sending if it exceeds the 1MB ingest limit.

Bug fixes

Fix duplicative log payloads on unload

Ensure agent clears buffer on page navigation unload harvests to prevent duplicative payloads from being sent.

Ensure drain target is a valid event emitter before subscribing

Ensure that the drain target is a valid event emitter to ensure that the .on method exists and will not throw errors.

Telative timestamps in session trace

In rare cases where PerformanceNavigationTiming API is undefined, session trace timing nodes would be reported using epoch timestamp values instead of relative timestamp values. This would result in a broken session trace experience in New Relic. If the PerformanceNavigationTiming API is unavailable, the epoch timestamps will now be converted to relative timestamps accounting for user clock difference with New Relic servers.

Updated logging API function

Fix an issue where the logging API method would always result in an uninitialized agent warning and would not capture the log.

Security fixes

Apply obfuscation rules to session trace

A bug was introduced in version 1.259.0 where session trace data was not being processed through configured obfuscation rules. This fix ensures session trace data is properly obfuscated.

Potential areas where un-obfuscated data could be added to the session trace:

When calling newrelic.addToTrace, the name of the trace event is a string provided by the customer.
When capturing session trace nodes for ajax requests, the node will contain the current page URL excluding query parameters and hash fragments.
When capturing resources being loaded on the page (javascript and css files), the session trace node will contain the URL of the resource excluding query parameters and hash fragments.
When a user clicks a link on the page containing an href that includes a hash fragment and does not result in a hard page load, the href value of the link will be captured in a session trace node.
When the browser agent captures an error on the page, the message of the error is included in a session trace node.

Support statement

Consistent with our browser support policy, v1.265.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 117-127, Edge 116-126, Safari 16-17, and Firefox 118-128. For mobile devices, v1.265.0 was built and tested for Android OS 14 and iOS Safari 16-18.

Browser agent v1.267.0

Mon, 23 Sep 2024 00:00:00 +0000

v1.267.0

Features

Upgrade to web-vitals v4

Upgrade to web-vitals v4. For more info, please see https://github.com/GoogleChrome/web-vitals/blob/main/docs/upgrading-to-v4.md.

Improve notifications of stylesheet status for session replay

The agent reports internal metadata about the status of stylesheets on the page when collecting session replay information. This process was spotty and the logic has been improved to make the metadata more consistent. The ability to turn off "inlining" the stylesheets has been removed, as that behavior is required for the UI to re-render the replay.

Add soft navigations to Browser-Agent loader

Add the Soft Navigations limited preview feature to the default Browser Agent loader accessible via NPM.

Update TimeKeeper Source of Truth

Update the Agent's TimeKeeper to evaluate a timestamp provided directly by the consumer instead of a generic Date header, which should provide more control stability and granularity to the time synchronization processes.

Bug fixes

Improve reliability of customMasker

The customMasker method of the Session Replay feature has been fixed to be more reliable with DOM elements that do not fit web-standards, as to not throw errors when processing. Initial Replay harvests will now be gated until a valid snapshot is taken.

Stringify now returns an empty string if failed to transform

An internal mechanism used to convert objects to strings would return undefined if an exception was thrown during the process. This could lead downstream users of that method to throw errors if they expected the output to be a string. The utility method now always returns a string.

Support statement

Consistent with our browser support policy, v1.267.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.267.0 was built and tested for Android OS 14 and iOS Safari 16-18.

Browser agent v1.268.0

Tue, 08 Oct 2024 00:00:00 +0000

v1.268.0

Features

Aggregate UserActions

Utilize sequential aggregation techniques when observing UserAction data to reduce ingest cost for customers.

Add UserAction to GenericEvents

Select user interactive events will be captured in this release. This is an extension of the GenericEvents feature meant to drive UI experience.

Bug fixes

Always return a string for custom stringify method

An internal mechanism used to convert JS values to string was returning undefined for certain values, which may lead to errors for downstream callers when they are expecting a string. This is part 2 of a patch to ensure a string is returned.

Force generic events feature to clear buffer when unloading

Fixed an issue where the generic events buffer was not clearing when unloading. This affected a small portion of experiences where the agent was "unloading" due to the page losing focus, but not actually closing. Subsequent harvests when the page was re-focused would have the potential for duplicated data.

Support statement

Consistent with our browser support policy, v1.268.0 of the browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.268.0 was built and tested for Android OS 14 and iOS Safari 16-18.

Browser agent v1.269.0

Wed, 16 Oct 2024 00:00:00 +0000

v1.269.0

Features

Include logging feature in micro agent loader

Allow the MicroAgent loader on NPM to utilize the logging APIs to manually capture log data.

Add instrumentation metadata to logging

Add instrumentation attribution to logging payloads to fortify categorization and billing calculations in New Relic platforms. These attributes are dropped during processing and before storing the data and as such don't affect customer billing rates.

Bug fixes

Only ever allow session traces to capture page load timings once

An edge case issue was resolved where session traces could include duplicate copies of the page load timings obtained from the browser timing APIs.

Handle Session Replay Security Policy Errors

Handle Security Policy Errors encountered by session replay when browser APIs have been natively disabled. This was also observed to happen in Chromium browsers that completely disabled cookie storage. Supportability metrics about agent internal errors are now captured as a biproduct of this work to help facilitate future improvements.

Support statement

Consistent with our browser support policy, v1.269.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 119-129, Safari 16-17, and Firefox 119-129. For mobile devices, v1.269.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.270.0

Tue, 22 Oct 2024 00:00:00 +0000

v1.270.0

Features

Remove supportsSendBeacon runtime property

Removes the supportsSendBeacon runtime property from our agent code. We no longer officially support browsers that cannot use the sendBeacon method, so there's no point in checking for it.

Add Firefox to LCP test matcher

Add Firefox versions 122 and above to LCP test matcher since versions 122 and above now support collection of LCP web vital timings.

Remove 'pageHide' from page end-of-lifecycle listener

Remove pageHide from page end-of-lifecycle listener since browser agent support for Safari 14.4 is deprecated

Move deregisterDrain method to feature-base

Moves the deregisterDrain method in order to standardize the implementation pattern to match the drain method.

Relocate aggregator from loader and improve agent internals

Styling and architectural changes that will reduce agent loader size by moving the Aggregator module to async chunk and removing the need for some configuration getters in the features. No behavioral change or significant performance impact from the agent is expected.

Support statement

Consistent with our browser support policy, v1.270.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.270.1

Wed, 23 Oct 2024 00:00:00 +0000

v1.270.1

Bug fixes

Remove undefined agentRuntime in Session Trace

Remove an outdated reference to agentRuntime variable in the Trace feature released in 1.270.0. It caused undefined errors in sub-cases wherein max harvest nodes were reached.

Support statement

Consistent with our browser support policy, v1.270.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.1 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.270.2

Mon, 28 Oct 2024 00:00:00 +0000

v1.270.2

Bug fixes

Correct naming for logging pageUrl attribute

Corrects naming for the Logging pageUrl attribute by using the original url of the page instead of the url of when the event happens. Removes origin attribute from the runtime model object.

Support statement

Consistent with our browser support policy, v1.270.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.2 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.270.3

Thu, 31 Oct 2024 00:00:00 +0000

v1.270.3

Bug fixes

Ensure all lazy loaded modules issue warning instead of errors

Lazy loaded modules that are blocked from loading by third-party tools (such as ad blocking mechanisms) will issue a warning to console instead of throwing an error.

Support statement

Consistent with our browser support policy, v1.270.3 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.3 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.271.0

Fri, 01 Nov 2024 00:00:00 +0000

v1.271.0

Features

Ignore unhandled promise rejections that lack a valid reason

The agent will not report unhandled promise rejections that lack a reason property as they cannot generate sufficient stack trace or messaging information for debugging.

Support statement

Consistent with our browser support policy, v1.271.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 121-131. For mobile devices, v1.271.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.272.0

Thu, 07 Nov 2024 00:00:00 +0000

v1.272.0

Features

Marks and measures

Add detection for marks and measures which captures data as a BrowserPerformance event. This feature is being shipped in an experimental state and is off by default. To opt in to using this feature, it can be turned on by setting the config value init.performance.capture_marks = true or init.performance.capture_measures = true in Copy/Paste or NPM installations.

Support statement

Consistent with our browser support policy, v1.272.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.272.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.273.1

Mon, 18 Nov 2024 00:00:00 +0000

v1.273.1

Bug fixes

Multiple MicroAgent undefined session and limit available API

MicroAgent class now only shows the relevant API for use with NPM. The set is limited to methods that relate to features available with the MicroAgent. An issue with missing session when multiple MicroAgents are initialized is also fixed.

Support statement

Consistent with our browser support policy, v1.273.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.273.1 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.274.0

Tue, 19 Nov 2024 00:00:00 +0000

v1.274.0

Features

Upgrade SessionReplay libraries to latest version

Upgrade underlying session replay libraries to latest version which addresses some known bugs. This change also removes the error swallower inside the session replay module and instead handles all session replay errors at the window level to allow for external libraries to observe known errors to induce fallback behaviors, such as those implemented in CSS-as-JS libraries.

Support statement

Consistent with our browser support policy, v1.274.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.274.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.273.0

Mon, 11 Nov 2024 00:00:00 +0000

v1.273.0

Features

Refactor feature storages

This change rewrites the way every feature stores its respective data to optimize runtime overhead, improve agent internals efficiency, and standardize the way storages are referenced and called.

Remove wrap-events usage from soft nav

Remove wrap-events module from usage for soft navigation feature. This is part of an effort to cleanup code in the agent.

Support statement

Consistent with our browser support policy, v1.273.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.273.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.275.0

Tue, 03 Dec 2024 00:00:00 +0000

v1.275.0

Features

Allow logs API wrapper to update custom attributes

This supports the rollout of the auto-logging feature without disrupting customers that may currently be using wrapLogger to wrap the console object.

Enable the browser agent to run in extension background contexts

Use fetch to send harvest payloads when XMLHttpRequest is unavailable, such as in browser extension contexts.

Bug fixes

Harvest generic events when max size is reached

To avoid behavior that could lead to more network requests than necessary, generic events will now harvest early when the max payload size is reached. This represents an increase from 64Kb to 1Mb.

Support statement

Consistent with our browser support policy, v1.275.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.275.0 was built and tested for Android OS 15 and iOS Safari 16-18.

Browser agent v1.276.0

Mon, 16 Dec 2024 00:00:00 +0000

v1.276.0

Features

Allow feature flags to control experimental features

Use internal feature flags to control experimental features, reducing your effort and supporting APM-injected installations.

Capture Page Resource Assets

Add detection for page resource assets that captures data as a BrowserPerformance event. This feature is being shipped in an experimental state and is off by default. To opt in to using this feature, it can be turned on by setting the config value init.performance.resources.enabled = true in Copy/Paste or NPM installations.

Bug fixes

Ignore reserved attribute names on `UserActions` tied to the window

Force the agent to not capture target-level attributes for window-level UserActions. You can set window-level variables that mimic HTML element attributes like type or tagName. This change prevents the potential capture of those attributes as part of blur or focus user actions tied to the window.

Fix syntax error in fallback when tracking xhr readyState

Fixed the syntax error that would cause xhr readystate fallback checks to always capture.

Support statement

Consistent with our browser support policy, v1.276.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.276.0 was built and tested for Android OS 15 and iOS Safari 17-18.

Browser agent v1.277.0

Wed, 18 Dec 2024 00:00:00 +0000

v1.277.0

Features

Add custom events API

Add a new API - recordCustomEvent(eventType, attributes). This allows any custom-defined eventType to be stored in NRDB. Check the API documentation for more information.

Bug fixes

Soft navigation bug fixes and new soft navigation tests

Fixes several issues tied to the soft navigations feature. Calling newrelic.interaction() prior to a page load now creates a separate "api" trigger node. Multiple interactions managed simultaneously now have correct timings. Fixes a bug in soft navigation, where API-triggered interactions fail to close under default heuristic (URL + DOM change), because the mutation observer is not started. Finally, 'popstate' events are now valid interaction triggers for soft navigations.

Support statement

Consistent with our browser support policy, v1.277.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.277.0 was built and tested for Android OS 15 and iOS Safari 17-18.

Browser agent v1.278.0

Tue, 07 Jan 2025 00:00:00 +0000

v1.278.0

Features

Centralized harvesting

Introduces a singleton harvester tasked with sending feature payloads rather than each feature utilizing their own scheduler. This reduces runtime space usage and the number of timers which proportionally scales as the number of features increases.

Support statement

Consistent with our browser support policy, v1.278.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.0 was built and tested for Android OS 15 and iOS Safari 17-18.

Browser agent v1.278.1

Wed, 08 Jan 2025 00:00:00 +0000

v1.278.1

Bug fixes

Make Metrics harvest only on EoL for new Harvester

Prevent Metrics feature from harvesting on interval after changes in v1.278.0. This reverts its behavior back to sending only final harvests.

Support statement

Consistent with our browser support policy, v1.278.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.278.3

Tue, 14 Jan 2025 00:00:00 +0000

v1.278.3

Bug fixes

Change obfuscator to read dynamically from configuration

Fix an issue where obfuscation rules are not honored if added after the agent has initialized. Some user cases require obfuscation rules to be dynamically added, this change will allow that behavior -- as long as the obfuscation rules are added to newrelic.initializedAgents[index].init.obfuscate

Support statement

Consistent with our browser support policy, v1.278.3 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.3 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.278.2

Thu, 09 Jan 2025 00:00:00 +0000

v1.278.2

Bug fixes

Allow the page view feature to have access to an event buffer

Fix an issue where if the page unloaded before the page view feature could "block" itself from future harvests, an undefined error could be thrown when the harvester tries to access each feature's event buffer. The page view feature now has access to the event buffer, to prevent that undefined check. The event buffer will remain empty, since the page view feature does not carry state. This change rectifies an issue observed in 1.278.1.

Support statement

Consistent with our browser support policy, v1.278.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.2 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.280.0

Fri, 31 Jan 2025 00:00:00 +0000

v1.280.0

Features

Remove agentIdentifier argument from agent constructors

Removes the agentIdentifier argument from the Agent and MicroAgent class constructors. The agentIdentifier should always be a random hex string to guarantee uniqueness across agent instances.

Bug fixes

Roll back to previous FirstInteraction implementation

Setting agent back to previous FirstInteraction implementation after some reports of slow downs around the performance observer on the first input of a page.

Support statement

Consistent with our browser support policy, v1.280.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.280.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.279.0

Fri, 24 Jan 2025 00:00:00 +0000

v1.279.0

Features

Remove FID

First Input Delay (FID) has been deprecated and replaced by Interaction To Next Paint (INP). PageViewTiming events for first interactions are preserved by detecting the first first-input event and will no longer output value for the firstInputDelay and loadState attributes. For more info on PageViewTiming, see https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/. For more info on INP and the FID deprecation, see https://web.dev/articles/inp.

Debounce window user actions

Debounce focus and blur events on the window for 500ms to prevent duplicate events from being harvested. All major browsers have their own quirky behaviors that generate duplicate blur and focus events under some conditions. This change ensures that only 1 blur or focus event can be captured every 500ms to reduce noise.

Capture details in marks and measures

The detail property of PerformanceMark and PerformanceMeasure events will now be captured in New Relic BrowserPerformance under the entryDetail attribute. If detail is an object, it and any nested objects within it will be flatten into string path keys prefixed with entryDetail. See the PR for elucidation.

Add HTTP codes for harvest retry attempts

Agent will begin to retry harvests to the endpoints that failed for the following additional status codes: 502, 504, and 512-530. This is suggested by New Relic ingest teams as a possibility to recapture lost data in these marginal cases.

Support statement

Consistent with our browser support policy, v1.279.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.279.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.281.0

Tue, 04 Feb 2025 00:00:00 +0000

v1.281.0

Features

Capture Nearest UserAction Fields

The UserAction feature has been extended to capture "nearest" field values when the UserAction target does not include the desired fields. To facilitate this, a configuration was added allowing the user to control what fields are collected, specified as init.user_actions.elementAttributes: []. When empty, no extra fields will be collected. When supplied, the target will be checked for each property. This configuration defaults to ['id', 'className', 'tagName', 'type'], which matches the fields captured before this change.

For each elementAttribute defined, if the property is not found, the agent will search up the parent tree of the target element, until the property is found. If found up the parent tree, a property called "nearest" + fieldName will be added to the event.

Support statement

Consistent with our browser support policy, v1.281.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.281.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.279.1

Tue, 28 Jan 2025 00:00:00 +0000

v1.279.1

Bug fixes

CLS timing node not being reported post new Harvester

Reintroduce the cumulativeLayoutShift timing of PageViewTiming events into EoL harvests. After v1.278.0, this timing stopped being sent when the user leaves the page, resulting in a drop in CLS counts. The node contains attributes that aid in identifying the cause of bad scores.

Support statement

Consistent with our browser support policy, v1.279.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.279.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.283.0

Tue, 18 Feb 2025 00:00:00 +0000

v1.283.0

Features

Add global custom attributes to log data

Add custom attributes set by the setCustomAttributes method in Browser Agent API to logging data. These attributes are in the common.attributes section of the outgoing payload. Local custom attributes set by the log and wrapLogger APIs take precedence in the backend over the global custom attributes set by the setCustomAttributes API.

Add auto-logging feature

Introduces automatic observation of browser console methods to capture logging statements from the browser console across a given session automatically. On/off, logging level, and sampling are controllable via the application settings section of your browser entities. Check the getting started guide for more info.

Support statement

Consistent with our browser support policy, v1.283.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.282.0

Thu, 13 Feb 2025 00:00:00 +0000

v1.282.0

Features

Re-implement wrap-websocket into agent

Re-implement wrap-websocket code using ES6 extends syntax into the agent. This will allow supportability metrics to be reportable from websocket API usage.

Support statement

Consistent with our browser support policy, v1.282.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.282.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.283.2

Fri, 21 Feb 2025 00:00:00 +0000

v1.283.2

Bug fixes

Add logging analytic metrics and fix browser performance metrics

Fix logging analytics metrics and centralize the metrics reporter for easier use

Support statement

Consistent with our browser support policy, v1.283.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.2 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.284.0

Tue, 04 Mar 2025 00:00:00 +0000

v1.284.0

Features

Remove FID, replace first interaction detection with INP

First Input Delay (FID) has been deprecated and replaced by Interaction To Next Paint (INP). PageViewTiming events for first interactions are preserved by detecting the first INP event and will no longer output value for the firstInputDelay attribute. For more info on PageViewTiming, see https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/. For more info on INP and the FID deprecation, see https://web.dev/articles/inp.

Bug fixes

Deduplicate Prefixes on Unhandled Promise Rejection Messages

Remove an issue that caused Unhandled Promise Rejection: prefixes on casted error messages to be duplicated if already supplied on rejection reason messages.

Upgrade rrweb to 18

Upgrade RRWeb dependency to version 18 to improve session replay performance.

bump web-vitals from 4.2.3 to 4.2.4

Bumps web-vitals from 4.2.3 to 4.2.4 to fix memory leak in registering new event listeners on every keydown and click (#554)

Guard against non-CSSStyleSheet when fixing sheets for replay

Nullish values in the global styleSheets API can break implementations with the weakMap object tracking their status, throwing an error similar to TypeError: Invalid value used in weak set at WeakSet.add.... This fix checks that the value is acceptable before adding.

Support statement

Consistent with our browser support policy, v1.284.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.283.1

Wed, 19 Feb 2025 00:00:00 +0000

v1.283.1

Bug fixes

Removing websocket wrapping & SM

Removing websocket wrapping and metrics. WS instrumentation may be re-implemented behind a feature flag at a later time.

Support statement

Consistent with our browser support policy, v1.283.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.284.1

Tue, 11 Mar 2025 00:00:00 +0000

v1.284.1

Bug fixes

Obtain FirstInteraction directly from performance API

To alleviate the potential performance impact of creating new performance observers to support legacy FirstInteraction timings, a change has been made to query the performance API directly for the presence of first-input data without the use of an observer at logical checkpoints.

Console error on some cross-origin requests without NR CAT header

XHR headers will be checked for the deprecated New Relic CAT header before calling getResponseHeader, which throws a console error if it does not exist for cross-origin requests.

Support statement

Consistent with our browser support policy, v1.284.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.285.0

Tue, 18 Mar 2025 00:00:00 +0000

v1.285.0

Features

Decorate harvest requests with ht (hasTrace) param

Decorate with ht (hasTrace) query param for all harvest requests except for blobs and logs endpoints. This helps support searching for browser data with associated tracing data.

Inspection events

Adds inspection events that detail when various agent-related events occur. These events can be listened to on the event listener 'newrelic' string type. Events include agent initialization, agent fully loaded, event buffered, event harvested, and api calls.

Bug fixes

Session Replay text masking for whitespace

There is an edge case where whitespace was being masked, which interferes with the layout/styling in session replays.

Logging mode on session update

Fixes a typo in the session update handler for logging feature. The loggingMode which controls feature output will be correctly set after its session mode value is updated from another tab or window.

Support statement

Consistent with our browser support policy, v1.285.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.285.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.286.0

Tue, 01 Apr 2025 00:00:00 +0000

v1.286.0

Features

Erase .api property on agent instance

The .api property of full and micro agents have been removed. The browser API methods are instead moved to the agent instance itself for ease of targeted access. This includes a minor fix of runtime loaderType for agents that are re-configured after load.

Reduce noise from `mousemove` events

There may be an edge case where a site performance can be impacted if the browser agent picked up mousemove events via addEventListener.

Handle duplicate agent APIs

Top-level interaction api calls are only responded to by the first exposed non-micro agent. This was changed to prevent issues for customers that run multiple agents together. The top-level interaction api should only be used to communicate with the main agent on the webpage. API calls on micro agents must instead be directly called on the respective micro agents.

Bug fixes

Patch `newrelic` event detail

There is an edge case where if there is a listener on the newrelic event (as described in the install docs) and any API call is invoked inside this listener, it will trigger an infinite loop.

Get string className for SVG elements

Change the nearestClass field for SVG elements to be a meaningful string name. The className of such elements is of type SVGAnimatedString and previously resulted in an empty object string.

Support statement

Consistent with our browser support policy, v1.286.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.286.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.287.0

Thu, 10 Apr 2025 00:00:00 +0000

v1.287.0

Features

Change architecture to help enable future Micro Front End support

Update the browser agent to support the future product decisions necessary to support micro front end architecture patterns from a single agent instance. This includes the addition of experimental APIs, intended to be used internally only to help support product development until future general availability (GA) is reached.

Support statement

Consistent with our browser support policy, v1.287.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.287.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.288.0

Wed, 16 Apr 2025 00:00:00 +0000

v1.288.0

Features

Prevent storing session data past session expiry

There may be edge cases where some Session Replay/Session Trace data could be stored even though the agent session has expired. Add instrumentation to detect such occurrences and skip storing these events for the time being.

Introduce isFirstOfSession attribute on InitialPageLoad events

To help support User Journeys, the isFirstOfSession custom attribute will be added to BrowserInteraction events of initial page load kind if the page is the first of a new session.

Bug fixes

Reset `notified` when replay stops recording

Resolves an issue where JavaScriptError events would be missing the hasReplay attribute after session recording is resumed (for example, from user clicking on another tab/tab going idle and then coming back to it).

Solve race condition in logging abort

If the logging feature aborted before the agent had set up the event buffer, it could throw errors. This was addressed by checking for the presence of the event buffer before running methods against it.

Support statement

Consistent with our browser support policy, v1.288.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.288.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.288.1

Fri, 18 Apr 2025 00:00:00 +0000

v1.288.1

Bug fixes

Ensure event buffer always exists

Ensure event buffers always exist to prevent race conditions between agent life-cycles and data storage.

Call handle directly for submitting SM

This fixes a bad reference to a parent function that is not accessible.

Support statement

Consistent with our browser support policy, v1.288.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.288.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.

Browser agent v1.290.0

Fri, 02 May 2025 00:00:00 +0000

v1.290.0

Features

Bundler tools exports

An optional Webpack splitChunks cacheGroup matcher is now available for users who build the agent via NPM. This matcher enables de-duplication and merging of the agent's lazy-loaded JavaScript into a single chunk. This single chunk loads post-page render, consistent with the behavior of our pre-built agent for APM and copy/paste implementations.

Set UserAction currentUrl before aggregation end

Set currentUrl on the first event of a user action instead of at the end of aggregation.

Improve lazy-loading optimization

Optimize our pattern to ensure that code-bundlers such as webpack can more effectively tree-shake the output to only include the relevant files needed to run the agent. This specifically helps reduce the bundle size, reduce the amount of lazy files generated, and streamlines "custom" agent builds used with NPM.

API Code Splitting

Split the API method definitions per feature instead of a single file shared across all loader types. This allows each loader to only instantiate the necessary APIs for the features included, and reduce overall bundle size for the "Lite" build as well as custom-built agents with NPM. A shell will still exist for non-initialized APIs to prevent errors from throwing on APIs used without the needed features.

Support statement

Consistent with our browser support policy, v1.290.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.290.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.289.0

Thu, 24 Apr 2025 00:00:00 +0000

v1.289.0

Features

Remove agent config cache and getters/setters

Removes agent internal configuration utility functions. No impact to agent functionality is expected. Build size have been reduced by this coding style change.

Support statement

Consistent with our browser support policy, v1.289.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.289.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.290.1

Wed, 21 May 2025 00:00:00 +0000

v1.290.1

Bug fixes

Silence setting getter only harvestCount message

The warning that results from the agent attempting to overwrite the runtime harvestCount will be correctly silenced.

Support statement

Consistent with our browser support policy, v1.290.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.290.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.291.0

Fri, 30 May 2025 00:00:00 +0000

v1.291.0

Features

Create the measure API

Adds the measure API to the newrelic global object. This API allows generating new BrowserPerformance data even if auto-detection of marks and measures is not enabled.

Bug fixes

Fix race between end of session and features aborting

Fix an issue where features would race with the session manager when a session ends. This required a check for session timings to match a given session and could create a state where a new session created from a pre-existing session would trigger a partial replay or no replay, and prevent the agent from sending trace data with a given replay.

Harvest first session trace payload immediately

For better consistency, implemented old behavior where the first ST payload is harvested immediately when the page loads. This helps ensure cases where replays are harvested but traces are not happen less frequently.

Support statement

Consistent with our browser support policy, v1.291.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.291.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.291.1

Fri, 06 Jun 2025 00:00:00 +0000

v1.291.1

Bug fixes

Prevent ST from holding onto Event refs in memory when aborted

Releases the Event entries the agent hold onto in Trace after it has aborted. This addresses a known case of memory leak caused by continuing to add those references to a Set that is never cleared.

Clean BrowserPerformance entryName for resources

The entryName attribute of resource type BrowserPerformance events will now have a cleaner URL, removing the hash fragment from reported URLs.

Add safeguards for addToTrace

Events created with addToTrace API, which have an invalid UNIX timestamp, emit a warning and return without creating the event.

Support statement

Consistent with our browser support policy, v1.291.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-18, and Firefox 128-138. For mobile devices, v1.291.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.292.0

Mon, 16 Jun 2025 00:00:00 +0000

v1.292.0

Features

Update `BrowserInteraction` and `previousUrl` definition

Update BrowserInteractions to use document.referrer for previousUrl values on initialPageLoad interactions instead of mirroring previousUrl and targetUrl. This enables better functionality for user journeys and provides more insight on page linkages.

Add more inspection events

Adds new inspection events to the agent. These events include the drain event, window lifecycle events such as navigate, load, DOMContentLoaded, and the session event which emits on changes to the agent's session state.

Bug fixes

Fix `finished` API `timeSinceLoad` value

Fixes an issue where the finished api was creating a timeSinceLoad value for PageAction data as the unix timestamp instead of a relative time value in seconds from the page origin.

Support statement

Consistent with our browser support policy, v1.292.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 127-137, Edge 127-137, Safari 17-18, and Firefox 128-138. For mobile devices, v1.292.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.292.1

Thu, 26 Jun 2025 00:00:00 +0000

v1.292.1

Bug fixes

fix custom attribute race condition precedence

Addressed a race condition that occurred between the local storage module reading and writing custom attributes locally and the API updating custom attributes in page memory.

Support statement

Consistent with our browser support policy, v1.292.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 127-137, Edge 127-137, Safari 17-18, and Firefox 129-139. For mobile devices, v1.292.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.295.0

Mon, 04 Aug 2025 00:00:00 +0000

v1.295.0

Features

Add error cause detection

Detect and report the cause attribute on captured JavaScriptError events. If the cause is an instance of an Error, the stack trace will be captured, otherwise the stringified contents of the cause will be reported. This will be queryable in JavaScriptError events under the attribute cause.

Bug fixes

Add monkey-patching warnings

Added detection and warnings for when expected globals have been monkey-patched before the agent has been executed on the page. This can cause unexpected behaviors and the intent is to inform customers of this behavior.

Calculate first and last timestamps from raw data

Ensure the agent manually calculates the first and last timestamps of a SessionReplay payload before harvesting to help improve consistency on the UI replayer.

Support statement

Consistent with our browser support policy, v1.295.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 128-138, Safari 17-19, and Firefox 130-140. For mobile devices, v1.295.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.296.0

Tue, 19 Aug 2025 00:00:00 +0000

v1.296.0

Features

Harvest traces early

Update agent to handle session traces the same way other features handle data as of 1.294.0, by allowing harvests at 16kb of size.

Bug fixes

Remove event buffer inspection event

Removes the event buffer inspection event to avoid a memory leak on using console.log with the newrelic window event listener.

Support statement

Consistent with our browser support policy, v1.296.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.296.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.293.0

Tue, 01 Jul 2025 00:00:00 +0000

v1.293.0

Features

Add "long tasks" internal message

Add an internal message indicating if a wrapped function qualifies as a "long task". This is to be used later in agent features to enhance future behaviors.

Emit SM on rum response invalid timestamps

Emit a supportability metric on receiving an invalid timestamp in the rum call response.

Bug fixes

Address issue keeping distributed traces from being disabled

Addressed a bug where the agent was able to capture distributed traces, even when distributed_tracing: false was supplied in the configuration.

Support statement

Consistent with our browser support policy, v1.293.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 127-137, Safari 17-19, and Firefox 129-139. For mobile devices, v1.293.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.294.0

Wed, 23 Jul 2025 00:00:00 +0000

v1.294.0

Features

Harvest early

The agent will now be able to trigger early harvests if certain criteria is met. This will help ensure that more payloads are kept and memory leaks are prevented. The agent will initiate an early harvest when a feature buffer size reaches 16KB, otherwise it will continue to harvest every 30 seconds as before. This new behavior will apply to the following events:

AjaxRequest
BrowserInteraction
BrowserPerformance
Custom Events
Log
PageAction
PageViewTiming
SessionReplay
UserAction

A separate effort will be conducted to enable early harvesting for timeslice metrics, javascript errors and session traces which use other mechanisms for storage in the agent.

Bug fixes

report empty previousUrl as undefined

The previousUrl attribute on BrowserInteraction events was reported as an empty string is cases where document.referrer is empty. This caused URL grouping to apply grouping on an empty string, leading to meaningless groups being appended to previousUrl. previousUrl is now reported as undefined to allow URL grouping to skip empty URLs.

Support statement

Consistent with our browser support policy, v1.294.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 128-138, Safari 17-19, and Firefox 130-140. For mobile devices, v1.294.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.297.0

Wed, 10 Sep 2025 00:00:00 +0000

v1.297.0

Features

Prevent early harvests when in retry period

Prevent the agent from harvesting early when being rate limited. If the ingest service returns a 429, the agent will replace its data and try the harvest again later. While that is happening, it will no longer be able to harvest early as new data comes in, until it successfully harvests.

remove newrelic meta attribute

Remove the reporting of the __newrelic meta attribute from outgoing replay payloads. This is being conducted as a measure to help save billable bytes for customers and reduce cost of use for Session Replay functionalities.

Bug fixes

Fix exceptions for null bodies arising from empty harvests

A change has been made to enforce that all cleaned payloads ensure a valid output. Before, an empty string passing through the body cleaning process could throw an error as the mechanism would return the body as null. Now empty strings will pass through untouched, allowing further processing to apply successfully.

Support statement

Consistent with our browser support policy, v1.297.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.297.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.

Browser agent v1.298.0

Fri, 19 Sep 2025 00:00:00 +0000

v1.298.0

Features

Factor long tasks into soft nav base interaction span

BrowserInteraction under soft navigation ("SPA 2.0") will extend in duration beyond DOM modification time until the point wherein no long tasks have been observed for 5 seconds. JavascriptError and AjaxRequest are not yet associated with such interaction during this extended period beyond the end of the original heuristic.

Bug fixes

Force LCP to report the original page URL

Allow LCP to report its pageUrl distinctly from the harvest URL. An issue was observed where soft navigations occurring before the LCP harvest would report the current page URL instead of the original page URL tied to LCP. This change allows LCP harvest nodes to report the original URL, regardless of the current page URL. The change should apply both to the pageUrl and targetGroupedUrl attributes.

Support statement

Consistent with our browser support policy, v1.298.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.298.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.299.0

Tue, 07 Oct 2025 00:00:00 +0000

v1.299.0

Features

Add Flutter supportability metric

Introduces a supportability metric to track browser agent usage in Flutter web applications.

Add user frustration signals to `UserAction`

Provide better insight into potential user frustrations for specific user actions via dead click and error click detections.

Evaluate the accuracy of cross-feature attribution

To support internal improvement benchmarks, add supportability metrics that evaluate the accuracy of attributes that indicate the state of a separate event, such as hasReplay or hasTrace.

Bug fixes

Fix `recordReplay` API inconsistencies

Fixes an issue where a late-called recordReplay API call would not successfully harvest data.

Support statement

Consistent with our browser support policy, v1.299.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.299.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.300.0

Tue, 14 Oct 2025 00:00:00 +0000

v1.300.0

Features

Remove usage of the marks and measures feature flag

No longer gates the agent by an internal feature flag. Measures will be enabled for all users by default unless turned off through the application settings.

Reduce hasReplay attribute false positive rate

Only set "hasReplay" attribute once a successful session replay harvest has been observed to help reduce false positives.

Bug fixes

Update typings for interaction API to reflect waitForEnd

Fixes an issue where the typing file defining the .interaction API was not decorated correctly to account for the optional waitForEnd argument as documented.

Address issues with dynamic require and Rollup.js

Fixes an issue that led Rollup.js to spawn the error Error: Could not dynamically require ... when building pages that included the MicroAgent loader.

Support statement

Consistent with our browser support policy, v1.300.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.300.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.297.1

Wed, 17 Sep 2025 00:00:00 +0000

v1.297.1

Bug fixes

Prevent double import of Session Replay aggregate class

Fixes an issue that was found where the Session Replay aggregate class could be double imported when using the newrelic.recordReplay API method while preloading was enabled.

Support statement

Consistent with our browser support policy, v1.297.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.297.1 was built and tested for Android OS 16 and iOS Safari 17-18.5.

Browser agent v1.302.0

Fri, 24 Oct 2025 00:00:00 +0000

v1.302.0

Features

Prepare agent to utilize v2 harvests for MFE registrations

Update the agent to handle harvests for registered targets to use the newly defined v2 endpoint schemas. This will act as the mechanism to handle client-side entity and relationship synthesis as well as ingest MFE specific data. This will be supported for Log, PageAction and JavaScriptError events, but is currently gated behind internal feature flags until a public preview is announced.

Bug fixes

User frustrations logic should be gated

Move user frustrations logic to browser scope only with FF gate in Generic Events instrumentation. This should avoid running extraneous wrapping logic and events related to user frustrations.

Improve accuracy in standalone AjaxRequest event start times

Adjusts a problem in the agent where start times of certain standalone AjaxRequest event payloads were reported relative to the page origin instead of relative to the first event in the payload, causing discrepancies when visualizing in NR1.

Support statement

Consistent with our browser support policy, v1.302.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.302.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.301.0

Tue, 21 Oct 2025 00:00:00 +0000

v1.301.0

Features

Switch to using NR fork of rrweb

Browser agent will now switch to using New Relic's forked version of rrweb for Session Replay instead of the original repository. This will allow browser team to custom tailor hotfixes for issues.

Bug fixes

Preserve agent attributes for log payloads

Adjust browser log payloads, such that agent-reserved attributes will take precedence over user-provided values if they happen to share the same name.

Support statement

Consistent with our browser support policy, v1.301.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.301.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.303.0

Thu, 13 Nov 2025 00:00:00 +0000

v1.303.0

Features

Allow consent API to be invoked without localStorage access

Allows the consent API to function without requiring localStorage access, by keeping common state in the agent that controls harvests. Applications must invoke the API on every hard page load when localStorage access is blocked.

Allow nested registrations

To facilitate inherent parent-child relationships with the planned register API, allow registered entities to expose their own .register() API for children of that entity to register with. Entities who register with the container agent will be related to the container. Entities that register under another registered entity will be related to both the container as well as the parent entity.

Additional validation to prepare agent for MFE registrations

Adding validation rules in the agent to prevent bad values for MFE target id and name in support of MFE/v2 registrations.

Add measure support to register API

Adds support for the measure API in the register response object. This is in support of the future micro front end offering planned.

Add useConsentModel functionality

Adds use_consent_mode init property and functionality. Adds the consent() API call. The consent model, if enabled, disallows agent harvesting unless consent is given through the consent() API call.

Retry initial connect call

To help prevent data loss, the agent will now retry the original "RUM" call an extra time for retryable status codes.

Add custom event support to register API

Adds methods for capturing custom events to the register API, to be used later when MFE support is established.

SMs for browser connect response

Adds supportability metrics for failed responses on initializing the page_view_event aggregate.

Bug fixes

Obfuscate custom attributes for logs added after PVE

Extends obfuscation to cover custom attributes on logging events added after the initial RUM/PageViewEvent harvest.

memoize promise context propagation to avoid safari hangs

Memoizes promise context propagation to prevent potential browser hangs in Safari by avoiding repeated context operations.

Support statement

Consistent with our browser support policy, v1.303.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.303.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.304.0

Wed, 03 Dec 2025 00:00:00 +0000

v1.304.0

Features

Warn message on session reset

Adds a warning code when an agent session reset happens so that we have better debugging on browser transition behavior.

Reduce Session Replay snapshot sizes

Use slimDOMOption = 'all' by default to reduce session replay snapshot payload sizes.

Bug fixes

Observe document.body after document is interactive

Addresses the scenario where MutationObserver.observe() was issued before document.body is available, causing Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'. error.

Support statement

Consistent with our browser support policy, v1.304.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 134-144. For mobile devices, v1.304.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.306.0

Tue, 16 Dec 2025 00:00:00 +0000

v1.306.0

Features

Control log API through separate RUM flag

Logs captured by the newrelic.log method will now be configurable through settings and controlled separately from wrapped logs. This allows one to be disabled without affecting the other, as in the case that only newrelic.log is desired and not auto instrumented console.

Ensure responseStart is valid before relying on onTTFB

Adds an extra validation step to ensure that responseStart of the nav timing entry is valid before relying on onTTFB to return valid data. The web-vitals library depends on that value to operate correctly, and without a valid TTFB response, the agent will not send the RUM call. This change ensures that fallback measures are taken when responseStart is invalid, to ensure a RUM call is sent more reliably, which helps compatibility with unsupported frameworks such as ElectronJS.

Bug fixes

Remove linebreak syntax from webpack output

Removes the newline character in webpack output to avoid issues with copy-pasting our script as a string inside code.

Support statement

Consistent with our browser support policy, v1.306.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 135-145. For mobile devices, v1.306.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.307.0

Tue, 06 Jan 2026 00:00:00 +0000

v1.307.0

Features

Make soft navigations feature the default SPA

Soft navigations feature is now the enforced running feature for SPA. The older and deprecated SPA feature cannot be selected or used as of this update.

Add resetSession option to setUserId() API

Introduces option to reset the browser agent session when updating a userid via the setUserId() API.

Ajax deny list wildcard support

Adds wildcard character support, with the * character, to the AJAX deny list feature which allows to substitute one or more characters in your deny list filters.

Support statement

Consistent with our browser support policy, v1.307.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.307.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.305.0

Wed, 10 Dec 2025 00:00:00 +0000

v1.305.0

Features

Improve agent compatibility with ChatGPT connector apps

Small tweaks were made to the agent to allow for better compatibility with the unique iframe constraints of ChatGPT connector applications.

Enable user frustrations for Pro/SPA agents

Officially releases dead click and error click detections for interactive elements to Pro and SPA agents.

Support statement

Consistent with our browser support policy, v1.305.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 135-145. For mobile devices, v1.305.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.309.0

Tue, 03 Feb 2026 00:00:00 +0000

v1.309.0

Features

Warn when more than one agent is running

Added a console warning when more than one Browser agent is running on the page.

Improve MFE tag setting

Enforce tags to be set for micro frontends by supplying an object of key-value pairs to the tags argument of the register(...) API. This allows for tags to be specified with an explicit value instead of only supporting boolean tags.

Add WebDriver detection attribute to PageView & PageViewTiming

PageView, PageViewTiming and initialPageLoad-category BrowserInteraction events will now report a webdriverDetected property corresponding to the navigator.webdriver set by the browser.

Bug fixes

Micro agent duplicate handlers

Fixes when micro agents are created in a staggered fashion, handlers for each agent is multiplied by the number of agents that follow. For example if there were two agents, the handlers for the first agent was registered twice. This had the effect of duplicating events + contents of harvest payloads.

allow child registrations from blocked parents

Allow blocked parent entities to still instantiate a child MFE when registering

Support statement

Consistent with our browser support policy, v1.309.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.309.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.310.0

Tue, 17 Feb 2026 00:00:00 +0000

v1.310.0

Features

better MFE timing handling

Improve the detection of script assets reported by the browser which power the MicroFrontEndTiming event's timeToFetch and timeToBeRequested attributes. This change also includes new assetUrl and assetType attributes to better illustrate the assets used to populate the timing data.

Removing old SPA feature & related wrappings entirely

This concludes the complete removal of the old SPA feature that is replaced by Soft Navigations feature. Since agent version 1.307.0, the default "SPA" was already switched over, so no breaking changes from this version are expected.

Capture MFE timings as MicroFrontEndTiming Events

Captures the lifecycle timings of registered entities in preparation for future micro front end product

Bug fixes

Update measure API types

Corrects an issue where the typings associated with the measure API did not accept PerformanceMark as a valid input for start or end values.

Support statement

Consistent with our browser support policy, v1.310.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 17-26, and Firefox 137-147. For mobile devices, v1.310.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.310.1

Thu, 19 Feb 2026 00:00:00 +0000

v1.310.1

Bug fixes

Enhance LCP entry with fallback attribution values

In cases wherein LCP is reported with no attribution entry from web-vitals, the agent will now pass on other default provided attributes such as timeToFirstByte instead of ignoring them.

Support statement

Consistent with our browser support policy, v1.310.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.310.1 was built and tested for Android OS 16 and iOS Safari 18-26.

Browser agent v1.311.0

Fri, 20 Mar 2026 00:00:00 +0000

v1.311.0

Features

agentIdentifier removal

Removed scoped references by agent identifier to simplify the agent architecture. All references are now stored directly within the agent reference, eliminating the need to blend agent references with scoped objects via lookup keys.

Attribute original page URL to all PageViewTiming nodes

Expanded pageUrl attribution to all timings, building on previous work for LCP. PageViewTiming events now report the original hard navigation URL for all node types, ensuring data consistency for SPA even if the URL changes before harvest.

improve MFE timing logic

Enhanced the agent's ability to identify the correct MFE script calling the register API. This improvement results in more accurate timing information for MFE environments.

Bug fixes

Enforce string IDs for new MFE registrations

Resolved an issue where non-string IDs caused errors during MFE entity synthesis. The agent now enforces string-based IDs and issues a warning if a different data type is provided.

Circular replacer removed reused objects from harvests

Fixed an issue where the internal stringify method removed shared pointers across harvest payloads, which occasionally caused missing params attributes on error harvests.

Update RegExp to prevent un-minimized webpack build issue

Replaced the $ character with its hexadecimal equivalent in regular expressions. This prevents Webpack from incorrectly replacing the character during the build process, which previously caused agent failures in unminimized builds.

Support statement

Consistent with our browser support policy, v1.311.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.311.0 was built and tested for Android OS 16 and iOS Safari 18-26.

Browser agent v1.312.0

Mon, 30 Mar 2026 00:00:00 +0000

v1.312.0

Features

Automatically Detect MFE Logs

Add support for automatic Micro Frontend (MFE) attribution of Log events. Previously, Log events were only ever automatically captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the given log method (such as console.log, console.info, etc.) to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the log method being triggered, that event will be attributed to the MFE instead of the container.

Automatically Detect MFE AJAX

Add support for automatic Micro Frontend (MFE) attribution of AjaxRequest events. Previously, AjaxRequest events were only ever captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the AJAX call to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the AJAX request being triggered, that event will be attributed to the MFE instead of the container.

Bug fixes

Session replays not working for Angular app running on Safari

Fixes an issue where session replays would fail to capture any recordings beyond an initial snapshot for Angular apps running on Safari.

Revert circular replacer

The circular replacer method applied to JSON.stringify operations was seen to cause lag in niche cases with deeply complex and nested objects emitted in quick succession such as in scroll event handlers. This method was revert back to a faster simpler operation to decrease performance bottlenecks.

Support statement

Consistent with our browser support policy, v1.312.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

Browser agent v1.308.0

Thu, 08 Jan 2026 00:00:00 +0000

v1.308.0

Features

add support for mfe tags with the register API

Adds support for adding entity tags through the usage of the register API

add child.id attribute to facilitate MFE cross-linking

Adds a child.id attribute to duplicated data to facilitate future cross-linking in the UI

Add "deregister" API

Adds support for deregistering a registered entity, for use with the upcoming Micro Front End support initiative.

add parent.type attribute to facilitate relationship synthesis

Adds the required parent.type attribute for future relationship synthesis during MFE ingest.

Add default close reason

Add a default close reason of unknown to WebSocket events whose close reason could not be determined.

Bug fixes

enforce non-null values on the numeric fields

Ensure that numeric fields are always reported on WebSocket events by defaulting to 0 instead of undefined

Clean WebSocket URLs

Remove hash fragments and query params from URLs reported on WebSocket events

Support statement

Consistent with our browser support policy, v1.308.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.308.0 was built and tested for Android OS 16 and iOS Safari 17-26.

Browser agent v1.312.1

Thu, 02 Apr 2026 00:00:00 +0000

v1.312.1

Bug fixes

.at causes issues in older browsers

.at() is not being properly transpiled and causing initialization issues, switched to indexing.

Support statement

Consistent with our browser support policy, v1.312.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.

Browser agent v1016

Thu, 19 Jan 2017 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

New features

Release ID API: A new API allows you to uniquely identify your current JavaScript version, enabling a richer error feature with source maps identification. Stay tuned for more information and documentation!

Improvements

Passive Scroll Event Listeners: Previously, the wrapped scroll event listener did not take advantage of an available performance optimization: the passive annotation. By including this annotation, our wrapped scroll listener will allow a non-blocking, smooth scrolling action.

Bug fixes

XHR With Credentials: Previously, when the agent would send data using an XHR, it would feature-check the withCredentials property and set it to true if it was available. However, older versions of IE do not allow modification of the withCredentials property on unsent XHRs. The agent now wraps the property assignment in a try/catch block to prevent errors.

How to upgrade

To upgrade your agent to the latest version, see Upgrade Browser agent.

Browser agent v1026

Mon, 20 Mar 2017 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

Improvements

Adjusted PageAction limits: Previously, we limited PageAction events to 120 per page load and only 20 events per harvest cycle, resulting in dropped data if a user sent more than 20 pageAction events in a single burst. Increasing the harvest time to 30 seconds also increases the event buffer, allowing users to send up to 60 events per harvest.
Improved time measurement: Previously, the agent used the system clock to calculate timing, and since the system clock may shift over the lifecycle of a page, the agent could occasionally report inaccurate or unexpectedly negative values. Going forward, the agent will use perfomance.now(), which is a monotonically increasing clock that starts from navigationStart. This change will result in more accurate timing for modern browsers.

Bug fixes

Preserve event listeners: Previously, if the agent doesn't load correctly it affected the functionality of add- and removeEventListener. These will now function the same whether the agent loads or not.

How to upgrade

To upgrade your agent to the latest version, see Upgrade Browser agent.

Browser agent v1039

Thu, 22 Jun 2017 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

Bug fixes

Do not instrument SPA without a wrappable XHR: In browsers that don't orchestrate the wrapping of XHR, the SPA agent does not collect event data, only metric timeslice data. The agent will still report SPA for browsers that support XHR wrapping. Mobile Safari and a few other browsers didn’t support wrapping the XMLHttpRequest, so they would not produce event data for instrumenting Single Page Apps. They still collect other types of metrics.
Support setTimeout with a string duration: When you call setTimeout with a string as the duration, browsers will cast this as a number, but the agent did not handle this correctly. We are now handling this case correctly.
Work around mutation observer memory leak in IE 11: We have discovered that MutationObserver in IE causes a memory leak, so the agent now will prefer setImmediate for IE, and use a resolved promise to schedule the wrapping in Edge (and other browsers that support promises).
Handle short recursive timers: Some libraries recursively set timers that left our interactions open. The agent now handles this by reducing the max time it will allow to be included in the interaction.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1059

Mon, 02 Oct 2017 00:00:00 +0000

Notes

This Browser agent version has been temporarily removed; the most up-to-date version is currently agent version 1044.

The Browser agent, sometimes called the JavaScript agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

New features

Added JSONP support (relevant only for PRO+SPA): Browser Interactions that include JSONP requests are now correctly tracked. Previously, browser interactions that included JSONP were ended early and not included in the Breakdowns tab.

Bug fixes

Fixed a compatibility issue with zone.js: When New Relic and Zone.js v0.8.13 were used together, the context (this) was not being set correctly in some of the addEventListener calls used by clients.
Correctly send data when methods aren't wrappable: When XHR was not wrappable, the agent did not send data to the collector via XHR in some edge cases. We are now correctly sending the data if XHR exists on the page, even if it's not wrappable.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1044

Mon, 17 Jul 2017 00:00:00 +0000

Notes

Bug fixes

Improved Agent Performance: Improvements to how the agent verifies interactions are complete by setting and clearing multiple timers. Previously, the agent would make many unnecessary calls to clearTimeout, and will now only clear timers when appropriate.
Protect against custom events: Improvements to how the agent determines the event origin for Session Traces. In some libraries that use custom event wrappers, when the agent calls target on an event it can throw an exception. The agent now catches these types of exceptions when building Session Traces.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1071

Mon, 04 Dec 2017 00:00:00 +0000

Notes

New features

Link JS Errors to Browser Interactions (relevant only for PRO+SPA): When a JS error occurs inside a browser interaction event, the error will now be associated with the interaction via Insights attributes.

BrowserInteraction, AjaxRequest, and BrowserTiming events will now have the following attributes: browserInteractionId, eventId, and parentEventId.

Bug fixes

JSONP Tracking Breaks in some versions of Safari (relevant only for PRO+SPA): Previously, the agent would cause Safari browsers to lock up when JSONP requests returned large data. The agent no longer calculates JSONP response size.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1099

Thu, 04 Oct 2018 00:00:00 +0000

Notes

New features

Action Text: The agent now captures the text of the HTML element that was clicked when a browser interaction started. This value is stored as an attribute called actionText on the BrowserInteraction events. There is also a new API actionText, which can be used to manually set the action text value.

Bug fixes

The agent now uses a fallback method for collecting data when sendBeacon fails: Browsers can return false from sendBeacon call when it cannot be completed. The agent now detects it and falls back to a different method to ensure data is captured.
Fixed calculating stackHash value in Safari 10 and 11: The stackHash value was not being properly calculated for global errors in Safari 10 and 11, causing incorrect grouping of errors across all browsers.
Fixed issue with calling fetch without any arguments: On certain versions of the Safari browser, calling fetch without any arguments is permitted. Other browsers, in contrast, do not allow this and throw an error. This also prevented the agent from working properly.
Removed response size calculation for streaming fetch calls: Previously, the agent cloned the response of a fetch call and read the response body in order to capture its size. In certain versions of the Safari browser this caused other clone calls to fail. As a result, the agent now only uses the content-length header, when available, to capture response size.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1118

Fri, 04 Jan 2019 00:00:00 +0000

New features

Custom attributes are now added to JavascriptError events: Custom attributes collected with the setCustomAttribute() and interaction.setAttribute() API methods are now added to JavascriptError events.
Updated the noticeError() API: The noticeError() API method now accepts a second argument for custom attributes. For more details and examples, see the noticeError() documentation.

Improvements

Updated the timing of when page URL is collected: The URL collected by the agent and used for page view names is now collected after the load event to account for redirects. Currently, we are using the referrer header value from the initial agent call for transaction naming and for URL attributes on Insights events. The agent also sends the URL value as a part of its payload to get around HTTP header stripping. This update brings this value on a par with the HTTP header by capturing it at the time the agent call is made.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1123

Fri, 19 Apr 2019 00:00:00 +0000

Bug fixes

Fixed issue with capturing AJAX status code in Angular apps: Angular calls abort() on the XHR object after it successfully finishes. This was seen by our instrumentation as a call that did not finish, and as a result status code was set to 0 and reported as a network error. This fix addresses this use case by capturing status code before the call is aborted.

Browser agent v1130

Tue, 16 Jul 2019 00:00:00 +0000

New Features

First Paint and First Contentful Paint values are now being collected: For browsers that support the Paint Timing API, these two values are now collected and made available as attributes on the PageView and BrowserInteraction (initial load) events.

Definitions for each attribute in BrowserInteractions and PageViews are available in the New Relic event data dictionary.
For more information about the Paint Timing browser compatibility, see the Browser compatibility and requirements documentation.
For more information about User-Centric Perceived Performance metrics, visit the Google Developers Web Fundamentals Guides on Performance.
Read more on our New Relic blog.

Improvements

Updated instrumentation of the History API: The history API methods are now instrumented on the History object constructor. This is to ensure that our instrumentation does not override other libraries that wrap these methods.
Updated instrumentation of DOM API methods: The DOM API methods used for JSONP instrumentation are now instrumented on the Node object prototype (as opposed to HTMLElement lower in the prototype chain). This is to ensure that our instrumentation does not override other libraries that wrap these methods.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1158

Thu, 19 Dec 2019 00:00:00 +0000

Notes

This agent release includes functionality to support the addition of cross-origin resource sharing (CORS) for Browser's distributed tracing feature. This agent will be rolled out prior to the feature availability in the UI. Please note that the Browser-distributed-tracing feature is only supported with our Browser Pro + SPA agent. Full feature availability delivered on Jan. 2, 2019.

Agent release schedule Browser distributed tracing CORS support

APM auto-injected agents: 12/19/2019
Copy/Paste agent: 12/30/2019

Distributed tracing for cross-origin AJAX calls

The agent can now add the newrelic distributed tracing header to outgoing cross-origin AJAX calls. The origins that the agent should add headers to must be defined in the distributed_tracing.allowed_origins configuration section. Users can now enable CORS from the Browser 'Application settings' page. For complete feature documentation, visit the Enable cross-origin resource sharing (CORS) section of our Browser data in distributed tracing documentation.

Browser agent v1153

Fri, 08 Nov 2019 00:00:00 +0000

New features

Support for End User Originated Spans in Distributed Tracing

New Relic now supports end-to-end distributed tracing with this release. For our Browser & APM Pro customers, you can now enable the Browser spans for any app that uses our Browser Pro + SPA agent.
This MVP includes support for same-origin AJAX requests that originate during a BrowserInteraction event. This AJAX request will be listed as the root entry span for a trace.

Learn More

For more details about APM & Browser agent version requirements and enablement, see our Browser Data in Distributed Tracing Page. Please note that not all APM agents are supported at this time.
For more details about all supported Span attributes, visit our Event Data Dictionary

Known Issues

Enabling Browser in Distributed Tracing for use with current versions of these language agents, Java, PHP, and C, will result in disconnected traces (single span traces for all Browser requests) and potentially the loss of APM transaction traces and spans. Please see the APM compatibility requirements for supported versions and estimated release dates.

New PageViewTiming Event to capture User Centric Perceived Performance metrics in real time

With this release, we are tying together the visual and responsiveness performance for our customer's site. With every page view, the agent is now capturing the time of the first interaction along with FID (First Input Delay). The existing paint timing metrics (First Paint and First Contentful Paint) are now collected even when they occur after the load event. All of these new metrics are captured on the new PageViewTiming events, available in Insights. This new event type is available for all agents, but requires a Browser Pro subscription.

Visit our New Relic Event Data Dictionary for a list of attributes and more details about the PageViewTiming event.

First Interaction

First Interaction timing captures the moment in time that a user first engages with a site. Within this timing, we also capture the type of interaction (click, key, mousedown, etc). This timing represents the first step in calculating the First Input Delay, which is the time from First Interaction to the moment that the site responds (is interactive).

First Input Delay

FID is a metric that tracks the delay between the time a user can attempt to interact with a part of the site (for example, when they click a link, tap on a button, or use a custom, JavaScript-powered control), and the time that the interface is able to respond to that interaction. We have all experienced situations where a webpage has visibly loaded, but when we try to click around on buttons or any JavaScript-powered interactive elements, nothing responds. This delay is what the FID metric tracks.

The FID metric is in some ways an intersection of the First Contentful Paint and Time to Interactive metrics. It lies in the middle of those two points, measuring the time between the FCP (and therefore when a first input can be made) and when the browser’s main thread is able to respond to any interactions. One major point of FID that differentiates it from Time to Interactive is that it requires a user to interact! TTI can be calculated without user input, so it is somewhat less powerful in the sense that it isn't providing any new information about my user's active experience or frustration, we can only assume that slow = bad. Why only consider the first input

Learn more

For more information and query examples, see our PageViewTiming event documentation.
For more information about the Paint Timing browser compatibility, see the Browser compatibility and requirements documentation.
For more information about User-Centric Perceived Performance metrics, visit the Google Developers Web Fundamentals Guides on Performance.
For more information about the difference between FID and TTI, see When Users Click: Tracking First Input Delay

Improvements

Browser interactions now wait on external scripts to finish loading: Browser interactions measure the time of all Javascript code that runs as a result of an interaction. The agent now includes the time it takes to load and execute external scripts. This is useful, for example, when the code started by an interaction must be loaded first (lazy loading).

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1169

Fri, 22 May 2020 00:00:00 +0000

New Features

Privacy: Added the ability for admin users to toggle cookie collection On/Off via Browser Application Settings UI

The agent now accepts new configuration privacy.cookies_enabled. When it is set to false (OFF), the agent doesn't write any third party cookies (JSESSIONID & NREUM) and it also notifies the intake server to not return a third party cookie. By default, all current and newly created applications will have this value set to true (ON), so there will be no change in the data currently being collected by the agent. Admin users must toggle the setting to OFF and redeploy the agent in order to see this change take effect. Once cookie collection is set to false, users should no longer see session information captured with their event data. If a session was already in progress, that data will continue to be collected until that session expires. New sessions should report a null value.

Please note that auto-injected apps will receive this update before the UI option is available. See release dates below.

To learn more about how New Relic Browser uses cookies, see our documentation. For more information on security considerations, specifically around cookies, visit our Security for Browser documentation.

Release Dates

Auto-injected apps - May 28, 2020
Copy/paste apps - June 1, 2020
Corresponding UI changes - June 1, 2020

Issues Resolved

Fixed issue with document XHR requests

In some cases, the agent was causing a DOMException error when getting the size of XHR responses for requests with document response type.

Browser agent v1167

Fri, 07 Feb 2020 00:00:00 +0000

Issue Resolution

Resolved a bug that caused a script error when the windowUnload event fired. This issue affected only Internet Explorer prior to version 9.

Browser agent v1163

Wed, 05 Feb 2020 00:00:00 +0000

New Features

With this release of the New Relic Browser agent, we now support new metrics, largestContentfulPaint and windowUnload, in our PageViewTiming event. With the release of Chrome 77, Google now reports a metric called largest contentful paint. This metric, LCP for short, reports the render time of the largest content element visible in the viewport, along with the element size and element Id values. This new metric comes after extensive research by Google. They found that the more accurate way to measure when the main content of a page is loaded is to look at when the largest element was rendered. Largest Contentful Paint is replacing First Meaningful Paint (which is now a deprecated metric) in Google Lighthouse as well. Additionally, LCP is considered the "field" equivalent to the Speed Index "lab" metric.

Largest Contentful Paint is updated over time, but captured and reported when one of these three criteria is met:

A user interacts with the page, thus potentially changing the content in the viewport
The user closes the page (the window unload event fires)
If no other other interaction happens, and we have received a LCP value, we will report that value after 1 minute has passed
If we have not received a value, and no interaction has occurred after a minute, we will simply wait until we have received any value for LCP. This would only occur for very high values (> 1minute) of LCP.

In addition to this metric, we added the windowUnload event to PageViewTiming, so you can see when your users are most commonly closing their sessions. This metric is supported by all browsers on both desktop and mobile devices.

For more information about these new metrics, supporting attributes and browser compatibility, visit our PageViewTiming documentation.

Issue Fixes

Fix to resolve repeated InvalidStateError errors associated with IE11 and some Edge versions.

How to upgrade

To upgrade your agent to the latest version, see Upgrade the Browser agent.

Browser agent v1184

Wed, 30 Sep 2020 00:00:00 +0000

New Features

Added support for custom attributes on PageViewTiming events

Custom attributes created using the setCustomAttribute API method will now be included in all PageViewTiming events.

Issue Resolutions

[SPA- BrowserInteractions] Fixed an issue resulting from too many fetch requests
- Resolved a bug throwing a null reference error during browser interactions where more than 128 fetch requests were recorded and distributed tracing was enabled.
[PageViewTiming] Fixed an edge-case issue with the paint timing instrumentation
- In cases when nothing was painted to screen before the load event, the agent would throw an error. We have added a guard for this scenario.
[PageViewTiming] Fixed issue with Largest Contentful Paint recording
- The browser agent stops recording largest contentful paint after 60 seconds on a page. We fixed an issue where recording continued beyond that threshold.

How to upgrade your agent

For instructions for upgrading your agent, please view our docs.

Browser agent v1177

Tue, 18 Aug 2020 00:00:00 +0000

New Features

We are excited to announce the release of Cumulative Layout Shift, the third and final metric in Google's Core Web Vitals. This metric is an important, user-centric metric for measuring visual stability because it helps quantify how often users experience unexpected layout shifts—a low CLS helps ensure that the page is delightful. The current set for 2020 Core Web Vitals focuses on three aspects of the user experience—loading, interactivity, and visual stability—and includes the following metrics (and their respective thresholds):

Largest Contentful Paint (LCP): measures loading performance. To provide a good user experience, LCP should occur within 2.5 seconds of when the page first starts loading.
First Input Delay (FID): measures interactivity. To provide a good user experience, pages should have a FID of less than 100 milliseconds.
Cumulative Layout Shift (CLS): measures visual stability. To provide a good user experience, pages should maintain a CLS of less than 0.1. For each of the above metrics, to ensure you're hitting the recommended target for most of your users, a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices. To learn more about the research and methodology behind these recommendations, see: Defining the Core Web Vitals metrics thresholds. Tools that assess Core Web Vitals compliance should consider a page passing if it meets the recommended targets at the 75th percentile for all of the above three metrics.

How does the Browser Agent report this data?

The agent now collects CLS (Cumulative Layout Shift) values as attributes on PageViewTiming events. CLS measures how much layout of the page shifts and is represented as a score. All types of PageViewTiming events (except FP and FCP) include this attribute, showing the score up until the point the timing measurement was taken. You can now track your CLS score throughout the page loading cycle to better understand and focus your optimization work on the moment in time where you are experiencing the worst scores.

We have also added two new events to the PageViewTiming event, pageHide and windowLoad to complete the full page load journey. These timings are useful with its CLS (Cumulative Layout Shift) attribute to paint the picture of a user's journey through the load experience.

The pageHide event represents the first time that the page was hidden (e.g. by switching browser tab). Note that we only collect the first pageHide events at this point.
The windowLoad event is fired when the whole page has loaded, including all dependent resources such as stylesheets and images.

For more information, please visit our docs on the PageViewTiming event.

Issue Fixes

[PageViewTiming event] Fixed unrealistic high values for FI & FID Older browsers report Event.timeStamp as an epoch time instead of value relative to the page navigation start. The agent took this into account for FI (First Interaction) timing values but not for FID (First Input Delay). With this fix, there should no longer be unrealistic outlier values for FID.

How to upgrade your agent

For instructions for upgrading your agent, please view our docs.

Browser agent v1194

Mon, 11 Jan 2021 00:00:00 +0000

Improvements

Optimized instrumentation of promises

The promise instrumentation has been updated to reduce performance overhead on web sites that use large number of promises.

Issue Resolutions

Fixed issue with SPA overhead

In a rare case where large number of callbacks are executed at the end of an interaction, the agent could cause a significant overhead. This has been fixed in this version of the agent.

Fixed issue with Fetch instrumentation

Updated fetch instrumentation to account for cases when the function argument is a URL object.

Browser agent v1173

Wed, 29 Jul 2020 00:00:00 +0000

New Features

Browser in distributed tracing now supports W3C trace context headers. W3C Trace Context is a standard that makes distributed tracing easier to implement, more reliable, and ultimately more valuable for developers working with modern, highly distributed applications. The standard greatly simplifies use cases where developers instrument services using tools from different distributed tracing solutions. Now all tracers and agents that conform to the W3C Trace Context standard can participate in a trace. Trace data can be propagated from the root service all the way to the terminal service.

Once Distributed Tracing is turned on in your Browser Application Settings page, the trace context headers will be added by default, along with the newrelic proprietary header, for same origin AJAX requests. If your system is fully configured to send w3c trace context throughout all services, you can choose to disable the newrelic header from the Application setting tab.

For cross origin AJAX requests already configured to accept the newrelic header, you can now select the option to send the W3C trace context headers. When selected, all origins defined must be configured to accept the traceparent and tracestate headers. For information on configuring CORS headers, please see our docs page for an example. As with the same origin requests, if you system is fully configured for W3C trace context headers, you can choose to disable the newrelic header.

For more information, please see our New Relic Support for W3C Trace Context blog post.

The following New Relic agents now support W3C:

Browser Pro+SPA agent 1173 and higher
Java 5.1.0 and higher
Python 5.5 and higher
Go 3.1.0 and higher
Node.js 6.4 and higher
Ruby 6.9.0 and higher
PHP 9.8 and higher
.NET 8.27 and higher

Browser agent v1198

Mon, 01 Feb 2021 00:00:00 +0000

Improvements

Updated mechanism for collecting data

The agent now sends JS errors and AJAX metrics data as body of a standard XHR request. This makes it possible to send more data than the maximum allowed length of URL query string.

Browser agent v1208

Thu, 11 Mar 2021 00:00:00 +0000

Improvements

Retry harvest network requests

The agent retries harvest XHR requests when it receives 408, 429, 500 or 503 response codes. Additionally, includes a security update to address NR21-01.

File protocol disallowed

The agent will not report any data when it is on a page opened from a local file.

Browser agent v1209

Wed, 26 May 2021 00:00:00 +0000

Improvements

Doubled the limit of PageAction events per harvest

Up to 120 PageAction events can be harvested every 30 seconds.

Removed call to /ping endpoint

Removed a legacy behavior used to ensure network connection was kept alive in IE 7/8/9.

Bug Fixes

Prevent duplicate session trace nodes

The final Session Trace node in a harvest, captured using the Resource Timing API, is no longer duplicated in the subsequent harvest.

This issue lead to 1 duplicate node in a Session Trace, every 10 seconds, over the duration of the trace.

Memory overhead when agent script

Fixed a memory leak in the agent when the network request to load the second part of the agent is blocked.

Update to file protocol restriction

Fixed an error thrown in the console when the agent is loaded using the file:// protocol caused by features in the agent trying to run when others had been aborted.

setTimeouts without callback functions

Fixed an issue where route change Browser Interactions would wait forever if a setTimeout was called without a callback function (passing code in as a string in the first argument) as the first argument.

Cypress.io

Fixed a conflict between the Browser agent and the Cypress.io test framework when instrumenting XMLHttpRequest.

Browser agent v1210

Wed, 30 Jun 2021 00:00:00 +0000

Improvements

PageHide PageViewTiming events are now accounted for during page unload events

PageHide PageViewTiming events are used to query CLS values. In cases where the page was never hidden, inconsistencies would arise because the PageViewTiming event with that type would not be collected. Now when pageUnload fires, if a pageHide PageViewTiming has not already been set, it will set it to the time of unload.

Perfect Cumulative Layout Scores (CLS) are now recorded as 0

Perfect CLS scores were being ignored, because a score was only recorded when content shifted. This change reports perfect scores as 0, fixing inconsistent CLS queries.

Record fetch calls as metrics

Fetch calls are currently only recorded as AjaxRequest events with SPA browser interactions. This change records fetch calls as AJAX metrics, which will make them visible in the AJAX UI charts.

Browser agent v1212

Mon, 08 Nov 2021 00:00:00 +0000

Improvements

Updated LCP tracking

Largest Contentful Paint will now stop being tracked when page visibility changes to hidden. This aligns with the web-vitals library.

Added passive flag to addEventListener calls

Using the addEventEventListener without the passive flag for the touchstart event is flagged in Lighthouse. The passive flag is now applied to all addEventListener calls in the agent.

Update to Cumulative Layout Shift calculation

The CLS calculation has been updated to use session windows in order to align with Google Chrome tooling (Lighthouse, PageSpeed Insights, CrUX). For more information, see the official blog post on web.dev.

Bug Fixes

Fixed issue with Array.isArray() call

Array.isArray() call is not supported on old browsers and can cause a runtime error. This call has been replaced with an alternative that works on older browsers.

Fixed issue with null function argument in the addEventListener API

When a null value was passed in to the addEventListener API, the agent would report an internal error. This edge case is now being handled.

Fixed issue with Ajax deny list

There was an edge case where certain ajax calls could have been excluded when they should not have been. This is now handled correctly.

Miscellaneous

Added support for collecting internal/supportability metrics

The agent can now send metrics that capture information about how the agent itself is working internally.

Added agent supportability metrics for tracking API usage

Added agent supportability metrics for tracking excluded Ajax events

Browser agent v1211

Wed, 06 Oct 2021 00:00:00 +0000

Improvements

AjaxRequest events for all XHR/fetch requests

Previously, XHR/fetch requests were captured as AjaxRequest events only when they were part of a route change. With this change, all requests will be captured as events. This feature can be further configured by specifying which requests should not be collected.

Span events are for all XHR/fetch requests

Previously, Span events were generated only for XHR/fetch requests that were part of a route change. With this change, all requests will be captured as Spans.

Update to Cumulative Layout Shift calculation

Bug Fixes

Prevent duplicate session trace nodes

The agent no longer calls the clearResourceTimings API, which had the potential to affect other scripts from accessing all resources. Instead, it now uses the PerformanceObserver API to collect information about resources.

Browser agent v1215

Tue, 25 Jan 2022 00:00:00 +0000

Improvements

Internal NR Platform release date: 01/24/2021
Production APM-injected release date: TBD
Production Standalone release date: TBD

Collect supportability metrics for frontend frameworks

Added frontend framework detection metrics to help guide future priorities for browser agent features. The following frontend frameworks will now be detected and analyzed:

React
Angular
AngularJS
Backbone
Ember
Vue
Meteor
Zepto
Jquery

Browser agent v1214

Thu, 06 Jan 2022 00:00:00 +0000

Improvements

Added NetworkInformation attributes to LCP & FI

The Largest Contentful Paint (largestContentfulPaint) and First Interaction (firstInteraction) PageViewTiming events will now include attributes from the NetworkInformation API (on compatible browsers) observed on the page. This includes network type (networkType), round trip time (rtt) and downlink (downlink).

Added element identification attributes to LargestContentfulPaint

LargestContentfulPaint PageViewTiming events will now include the elementTagName attribute which represents the triggering element's tag name. If the triggering element is an image, the event will also include the elementUrl representing the image URL if present.

Included page view timing data in session trace payload

If observed, the agent will now include PageViewTiming events in the session trace waterfall payload. These events will be available in an upcoming update to the session traces UI.

Added session trace IDs to harvests

If a session trace is active on a page, a session trace ID associated with that trace will now be appended to all subsequent events generated on the page for the linking of session-related datasets downstream. This ID will be appended to any payload that sent after a session trace has been started. PageView events are generated before session traces begin and will not contain this ID and in most cases Initial Page Load BrowserInteraction events complete before a session trace begins and are not guaranteed to contain this ID.

Bug fixes

Exclude Data URL requests from Ajax events and metrics

Previously, XMLHttpRequest and Fetch calls made with Data URLs could prevent the agent from harvesting data.

Browser agent v1222

Wed, 18 Jan 2023 00:00:00 +0000

New Features

EXPERIMENTAL - Unblock instrumented pages from the back/forward cache (w/ feature flag)

An instrumented page's back-forward cache eligibility was hampered by the agent's unload listener, which will be removed when a feature flag is on. With the allow_bfcache enabled in the init config, the agent's definition of (the end of) an user's session is more refined, and it will no longer be blocking the browser from utilizing its respective b/f cache.

Internal

Reduce size of builds for modern browser targets

The agent is now compatible with only modern web syntax (ES6+); this reduces loader size for these browsers by 20% or more. We target and test support for just the last ten versions of Chrome, Edge, Safari, and Firefox -- see browser agent EOL policy for more details.

Bug Fixes

Prevent feature from collecting and harvesting future data if account entitlements are invalid

The agent will now attempt to shut down an initialized feature if account entitlements are invalid. Accounts that lack entitlements to use certain endpoints will see many 403 errors in the console without this behavior. This behavior requires the Page View Event feature to be enabled.

Do not collect XHR events for data URLs

AJAX events for data URLs have not historically been collected due to errors in the agent when handling URLs without hostnames. Going forward, XHR calls to data URLs will not cause agent errors and will continue to be excluded from collection.

Fix nrWrapper exclusion in error stack traces

Restoring previous functionality whereby the nrWrapper agent method should be excluded from JavaScript error stack traces.

Fix errors with global self redefinition

Fixing an issue where external code redefining the self global variable causes the agent async loading to fail and the agent to crash.

Fix check for sessionStorage object

Ensure the agent does not crash when sessionStorage is not available or when the quota has been exceeded or set to 0.

Browser agent v1221

Thu, 15 Dec 2022 00:00:00 +0000

New Features

Add infrastructure to run on web workers

The agent's infrastructure will now allow for the agent to be built to run on web workers for future projects.

Bug Fixes

Expose webpack library as output type "self" vs. "umd"

To address "mismatched anonymous define" errors thrown by RequireJS, the agent's webpack library output will no longer include UMD checks for CommonJS and AMD module environments, and will instead be exposed globally via self.

Fix custom attribute handling in cases where the info block is loaded after initialization

Fixed an issue where custom attributes could be cleared and reset if the info block was included on the page below the loader script. Our guidance still remains that all configurations should be included on the page above the loader code, however this is an attempt to do no harm when feasible for backwards compatibility.

Update JS error bucketing algorithm

The agent will now take into account the error object type, message, and original stack trace when deciding on whether multiple JS errors should be bucketed together.

Fix initial page load interaction reporting with Nuxt

Fixed an issue where when using the SPA loader with Nuxt, the initial page load interaction was never being completed. This resulted in events like errors being retained in memory and never harvested because they were tied to an incomplete interaction.

Fix error with jsPDF library and SPA agent

Fixed an issue with the jsPDF library where it was not correctly detecting browser native support for Promises due to our wrapper. This resulted in an exception and jsPDF not generating the PDF. This issue is not present with the pro or lite agent.

Note: This issue does not affect the pro or lite agent. This change allows the jsPDF library to function correctly when the SPA agent is used. However, it does cause an internal error within the agent to be generated. This error does not break the agent, jsPDF, or other functionality. The issue is planned to be addressed in a future update.

Browser agent v1223

Fri, 27 Jan 2023 00:00:00 +0000

Support statement:

Refactor loader architecture for improved developer experience

This architectural release simplifies file structure and refactors the way features are composed, in preparation for future developer experience improvements. These changes are not anticipated to have impact on agent behavior or functionality.

Browser agent v1220

Fri, 07 Oct 2022 00:00:00 +0000

This release is in public preview. We're slowly rolling out these features to different browser agents based on the browser's instrumentation method. Here's the release timeline:

Internal NR Platform release date: 10/07/2022
Production APM-injected release date: 10/7/2022
Production Standalone release date: Estimated around 12/13/2022

New Features

Capture unhandled Promise rejections

The Agent now observes and captures unhandled Promise rejections as JavaScript Error objects.

Removed 3rd Party Cookies

The browser agent no longer uses 3rd party cookies to maintain and track session information. 1st party implementation using window.sessionStorage is now used, which is automatically cleared when a page session ends. This is still managed using the privacy settings form in your browser application settings.

LCP is no longer reported on initially-hidden pages

LCP metrics are no longer reported on pages whose state is hidden at load time, such as tabs refreshing in the background of a focused tab.

Async Module Loading

Individual features of the browser agent can now be dynamically loaded, enabled, or disabled at runtime.

Removal of script tag injection

The agent no longer inserts other features into the page via a script tag insertion. It now uses network requests to instantiate other code modules.

Updated test process

In an effort to better support the majority of our traffic, the test suite required to merge PRs has been updated to run against the latest 10 major versions of Chrome, Firefox, Edge, Android, and the latest 5 major versions of Safari and iOS. As part of this process, outdated code and polyfill libraries aimed at supporting deprecated browsers are no longer included in production builds by default.

Bug Fixes

Fixed issue with BrowserInteraction nodes generating circular references

BrowserInteractions no longer generate circular trees when they are self referential.

Remove non-ASCII characters from builds

Certain dependencies were appending non-ASCII characters to build files. These characters were affecting older Python agent implementations downstream that worked to parse and encode the agent snippet. The build files are now checked and cleaned of non-ASCII characters before shipping.

Browser agent v1225

Fri, 10 Feb 2023 00:00:00 +0000

New Features

Gracefully abort agent if not fully instantiated

When importing of agent code fails, as when content gets blocked, the agent will clean up memory, the global scope, and any wrapped or modified APIs as much as feasible.

Bug Fixes

Resolve Google indexing of agent relative paths

In previous versions, the agent script included relative paths to its lazy-loaded chunks, which Googlebot picked up and attempted to index as pages. This change removes those relatives paths from the loader and centralizes our lazy chunk loading of agent features.

Refactor wrapping of Promise object

The agent's wrapping of the Promise object has been refactored to address conflicts with third party libraries and to add newer methods available on the native object. The new wrapping implementation is more conventional and less error-prone.

Fix uncaught promise error introduced in v1223

In some cases of failure to import agent script chunk "629", an error was thrown rather than caught and logged as a warning. The uncaught promise error responsible for this unintended behavior has been fixed.

Browser agent v1224

Wed, 08 Feb 2023 00:00:00 +0000

New Features

Support SPA, XHR, and session trace features on Chrome for iOS

Previously, the agent didn't collect SPA browser interactions, XHR events, or session trace data in Chrome for iOS, which uses the webkit engine with modifications. The agent now collects the same data in Chrome for iOS as in other supported browsers.

Expose build version to newrelic global

The build version is exposed to the newrelic global object. You can access it with newrelic.intializedAgents[<agentID>].runtime.version.

Internal

Add automation for documentation site updates on new releases

A new release of the browser agent will automatically raise a PR to the documentation site with the relevant changelog items.

Bug Fixes

Fix multiple custom interaction end times

Fixed an issue where multiple custom interactions harvested at the same time would result in only one interaction being persisted in New Relic.

Prevent AJAX time slice metrics based on deny list

Prevent time slice metric collection for AJAX calls when such a call matches an entry in the AJAX deny list.

Bind navigator scope to sendBeacon

Some browser versions will throw errors if sendBeacon doesn't have the navigator scope bound to it. A fail-safe action of binding the navigator scope to sendBeacon was added to try to support those browsers.

Preserve unhandledPromiseRejection reasons as human-readable strings in error payloads

The agent will attempt to preserve unhandledPromiseRejection reasons as human-readable messages on the Error payload that gets harvested. The previous strategy didn't always work, because Promise.reject can pass any value, not just strings.

Fix missing interactions for dynamic routes in Next/React

Fixed an issue where when using the SPA loader with Next/React, route changes that lazy loaded components wouldn't be captured. While the issue specifically called out Next/React, this should apply to Nuxt/Vue and Angular.

Fix interactions missing API calls in Angular

Fixed an issue where when using the SPA loader with Angular, route changes that contained API calls, via Angular resolver, wouldn't capture the xhr/fetch on the interaction. This works with eager and lazy routes in an Angular SPA.

Browser agent v971

Wed, 17 Aug 2016 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

New features

Add support for keyboard change events [Pro+SPA]: Keyboard events will now automatically trigger a Browser Interaction timing.
Browser Timing Events now have Traced Callback Duration [Pro+SPA]: In order to match the attributes on other New Relic Browser related events, the Browser Timing events now include callback durations by default.

Improvements

Change harvest to not use sendBeacon: We now use the sendBeacon native API only for page unload. The agent will now attempt to use an XHR when available and save sendBeacon for unload events, in order to reduce the data transferred using the sendBeacon API.

How to upgrade

To upgrade your agent to the latest version, see Upgrade Browser agent.

Browser agent v1226

Thu, 23 Feb 2023 00:00:00 +0000

New Features

Enable back/forward cache

Updating the agent default configuration to enable the back/forward cache feature previously released in version 1222 by default.

Bug Fixes

Revert xhr deny list timeslice metrics

Customers were losing visibility into all calls on the page when denying timeslice metrics based on the deny list. This change reverts to the behavior seen in all previous versions of the browser agent.

Handle unhandledPromiseRejections more gracefully

The agent will attempt to handle niche objects throw from unhandledPromiseRejection events more gracefully. These cases could include objects with frozen or static properties, or custom extensions of the Error class without a set method in place.

Disable metrics for missing entitlement

Fixing issue where metrics harvesting was not being halted when the agent RUM call indicated the account did not have entitlement to the jserrors endpoint. Before this change, customers missing this entitlement would see network calls to the New Relic jserrors endpoint result in 403 or 409 errors.

Browser agent v974

Wed, 24 Aug 2016 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

New features

Added newrelic.setErrorHandler API to allow for selective ignoring of known errors [Pro, Pro+SPA]: This API takes a single error handler function, which will be called for each error the agent captures. If the handler returns true, the error will NOT be recorded by New Relic, otherwise it will be processed normally.

For details on how to use this API, see our Browser API Docs.

How to upgrade

To upgrade your agent to the latest version, see Upgrade Browser agent.

Browser agent v1216

Wed, 20 Apr 2022 00:00:00 +0000

Internal NR Platform release date: 04/19/2022
Production APM-injected release date: 04/20/2022
Production Standalone release date: 04/27/2022

New Features

Introduced obfuscation mechanism to payloads

Added internal mechanism for applying regex and replacement rules to all strings in payloads to obfuscate before sending to ingest.

Automatically obfuscate `file://` protocol

A change has been implemented in our handling of applications hosted locally on a file:// protocol. For security reasons, we can not send payloads that contain file information, so our previous implementation revolved around completely shutting the agent down when file:// protocols were detected. This change automatically obfuscates all file:// paths from our payloads before sending to ingest.

Bug Fixes

Fixed issue with trace ID random hex character length

The final character in trace ID hex generation was returning as undefined, which translated to always be 0 (undefined & 15 === 0). This change fixes this final character and ensures it is valid.

Browser agent v1227

Thu, 09 Mar 2023 00:00:00 +0000

New Features

Add INP and long tasks reporting

The interaction-to-next-paint metric is now calculated and reported at the end of user sessions, via the Google CWV library. In addition, long continuously executed and blocking scripts detected by the PerformanceLongTaskTiming API are also forwarded to New Relic. This latter functionality is off by default, until a curated UI experience is created to utilize this data.

Bug Fixes

Revert unwrapping of globals on agent abort

Partial revert of graceful handling change made in v1225 that unwrapped modified global APIs and handlers, which caused integration issues with other wrapping libraries and code.

Add resiliency around SPA interaction saving

Added resiliency code around SPA interaction node save functionality to ensure a cancelled interaction node without a parent further up the interaction tree does not cause an exception to be raised from the agent.

Internal

Add internal metrics to evaluate feasibility page resource harvests

Internal metrics were added to track the feasibility and impact of collecting page resource information using the PerformanceObserver resource timings, such as scripts, images, network calls, and more.

Collect supportability metrics at the end of page life

Collate all of the internal statistic metrics calls, which, as of today, are sent at page start and periodically into one call made when the end user is leaving the page.

Browser agent v998

Thu, 03 Nov 2016 00:00:00 +0000

Notes

The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent.

New features

Added the setCurrentRouteName API method [relevant only for Pro+SPA]: The agent now has an API method to set the current route name for the page. This api can be used to set the previousRouteName and targetRouteName for BrowserInteraction events.

For details on how and why to use this API, see our Browser SPA API Docs

Improvements

Disabled insecure communication with New Relic: Previously the agent would send RUM data to the router without TLS if the request was initiated from an insecure page. Now the Browser Agent will always use TLS connection when transmitting data.
Browser Agent no longer mutates the attributes object passed to the addPageAction API: Previously the agent would mutate the attributes object passed to add page actions by adding the default and page attributes onto this object.

Bug fixes

Fixed a compatibility issue with zone.js: Previously when the Browser Agent and zone.js were both included on a page, additional event handlers would be triggered twice. For example, when event handlers were added as properties, such as onreadystatechange, these handlers would be triggered twice in some browsers. This issue has now been resolved.
Fixed a bug with cross-frame callbacks: Previously, when adding event handlers for events in iframes, the agent would attempt to wrap the provided callbacks. When the wrapping logic called the callback belonging to another frame, a permissions exception would be thrown. The agent will now only wrap callbacks created in the same frame.
Fixed a memory leak when the Browser agent fails to load correctly

How to upgrade

To upgrade your agent to the latest version, see Upgrade Browser agent.

Browser agent release notes

Browser agent v1228

Bug Fixes

Fix negative offset timings

Browser agent v1.229.0

v1.229.0

Use semantic versioning scheme

Use web-vitals library for internal timing calculations

Ship the Browser Agent repository to NPM

Support statement:

Browser agent v1.230.0

v1.230.0

Add persistence for custom attributes

Add setUserId API

Fix npm package browser targets

Fix npm package exports

Fix npm package import for typescript projects

Add error catch around sendBeacon

Remove array reduce polyfill

Support statement:

Browser agent v1.231.0

v1.231.0

Omit CLS scores before web-vitals report them

Fix accepted argument type for all and race methods of Promise

Upgrade Navigation Timing API in PageView (RUM) call

Fix typo in top-level API causing exception

Add null entry checks to certain web-vitals handlers

Remove previously added console logging measurements

Rectify version reported by NPM agent implementations

Fix exception when importing NPM package source code

Support statement:

Browser agent v1.232.0

v1.232.0

Features

Minor changes to SMs

Add query parameter supportability metrics

Allow custom error grouping

Add new stateful Session Manager

Support statement:

Browser agent v1.232.1

v1.232.1

Bug Fixes

Add X-NewRelic-ID header only if defined

Identify inline stack trace URLs more precisely

Support statement:

Browser agent v1.233.0

v1.233.0

Features

Capture metrics for usage of MooTools and certain polyfills

Update agent internals in early preparation for new features

Bug Fixes

Address "configurable" warnings arising from user-agent module

Refactor usage of Array.from to address MooTools conflict

Ensure runtime is preserved for late-configuration cases

Support statement:

Browser agent v1.233.1

v1.233.1

Bug Fixes

Address bug affecting XHR harvest re-schedule

Support statement:

Browser agent v1.236.0

v1.236.0

Features

Expose MicroLoader in the npm package

Remove img, jsonp, and xhrGet methods

Bug Fixes

Handle chunk load promise error introduced in 1.235.0

Fix illegal invocation error on final harvest

Support statement:

Browser agent v1.237.0

v1.237.0

Features

Stop reporting ajax events going to same beacon

Add warning for large payloads

reduce jserrors wrapping and remove onerror use

Bug Fixes

Remove fetch keep-alive unhandled rejection

prevent invalid error stack traces

Defining agent api methods for ts types

Fix potential property of undefined errors

Use `web-vitals` library for internal timing calculations

Fix accepted argument type for `all` and `race` methods of `Promise`

Upgrade Navigation Timing API in `PageView` (RUM) call