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
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.
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.
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
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.
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.
v1.288.0
特徴
セッションの有効期限を過ぎたセッションデータの保存を防止する
エッジ ケースでは、エージェント セッションの有効期限が切れているにもかかわらず、一部のセッション リプレイ/セッション トレース データが保存される可能性があります。 計装を追加してそのような発生を検出し、当面はこれらのイベントの保存をスキップします。
InitialPageLoad イベントに isFirstOfSession 属性を導入する
ユーザー ジャーニーをサポートするために、ページが新しいセッションの最初である場合、 isFirstOfSessionカスタム アトリビュートが最初のページ読み込み種類のBrowserInteractionイベントに追加されます。
バグ修正
リプレイの記録が停止したらnotifiedリセットします
セッション記録が再開された後に JavaScriptError イベントでhasReplay属性が失われる問題を解決しました (たとえば、ユーザーが別のタブをクリックした場合、またはタブがアイドル状態になってから戻ってきた場合など)。
ログ記録の中止における競合状態を解決する
エージェントがイベント バッファを設定する前にログ機能が中止された場合、エラーがスローされる可能性があります。この問題は、メソッドを実行する前にイベント バッファの存在を確認することで解決されました。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
弊社のブラウザ サポート ポリシーに従い、 Browserの v1.288.0 は、 Chrome 124 ～ 134、Edge 124 ～ 134、Safari 17 ～ 17、Firefox 126 ～ 136 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.288.0 は Android OS 15 および iOS Safari 17-18.1 用に構築およびテストされました。
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
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.
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.
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
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.
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.
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
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.
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.
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
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.
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.
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
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.
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.
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
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.
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.
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
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.
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.