Browser Agent v1.314.0 Release Notes

src/content/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.314.0.mdx

@@ -0,0 +1,38 @@
+---
+subject: Browser agent
+releaseDate: "2026-05-04"
+version: 1.314.0
+downloadLink: https://www.npmjs.com/package/@newrelic/browser-agent
+features: ["Add ajaxRequest.id attribute","Improve PageViewTiming load timing capture","Adjust timestamps for clock skew due to machine sleep","Automatically Detect MFE User Actions","Allow Session Replay to retry payloads"]
+bugs: []
+security: []
+---
+
+## v1.314.0
+
+### Features
+
+#### Add ajaxRequest.id attribute
+Adds a unique identifier to all AjaxRequest events to facilitate direct queries and drilling-down into data in NR1 UIs.
+
+#### Improve PageViewTiming load timing capture
+The load timing is now more reliably captured for pages, inheriting the idea from web-vital's `onTTFB`. Before, it occasionally missed `loadEventEnd` from nav entry from a browser race condition, particularly for larger/longer-loaded pages, which caused load to be `0`.
+
+#### Adjust timestamps for clock skew due to machine sleep
+Certain linux and apple hardware can freeze the performance API clocks when entering deep sleep, which can cause inaccurate timestamps on New Relic events upon awakening. This introduces a new change which attempts to correct clock skew caused by frozen machines.
+
+#### Automatically Detect MFE User Actions
+Add support for automatic Micro Frontend (MFE) attribution of UserAction events via a `data-nr-mfe-id` data attribute. Previously, UserAction events were only ever captured globally by the container browser application. With this change, the agent now performs a parental chain lookup for elements associated with the action, identified by the `data-nr-mfe-id` attribute.
+
+To associate UserAction events with a registered MFE, add a `data-nr-mfe-id` at the root DOM node controlled by your MFE package that matches the ID supplied to the `register` API.
+
+#### Allow Session Replay to retry payloads
+Payloads failed with retryable codes will be re-harvested by the agent. Further session replay data will not be collected until the harvest retries successfully.
+
+## 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](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). 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](https://newrelic.github.io/newrelic-browser-agent-release/) for more information.
+
+Consistent with our [browser support policy](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), v1.314.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.314.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.