• /
  • EnglishEspañolFrançais日本語한국어Português
  • Se connecterDémarrer

Browser agent release notesRSS

April 2
Browser agent v1.312.1

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

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.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.

March 30
Browser agent v1.312.0

v1.312.0

Recurso

Detectar automaticamente logs do MFE

Adicionar suporte para atribuição automática de Micro Frontend (MFE) de eventos Log. Anteriormente, os eventos Log só eram capturados automaticamente de forma global pelo aplicativo de navegador do contêiner. Com essa alteração, o agente compara a assinatura da pilha de chamadas do método de log fornecido (como console.log, console.info, etc.) à assinatura da pilha de chamadas do módulo MFE que se registrou na API register. Se o arquivo responsável por se registrar no agente do navegador for encontrado na assinatura da pilha de chamadas do método de log sendo acionado, esse evento será atribuído ao MFE em vez do contêiner.

Detectar automaticamente MFE AJAX

Adicionar suporte para atribuição automática de Micro Frontend (MFE) de eventos AjaxRequest. Anteriormente, os eventos AjaxRequest eram capturados apenas globalmente pelo aplicativo de navegador do contêiner. Com essa alteração, o agente compara a assinatura da pilha de chamadas da chamada AJAX com a assinatura da pilha de chamadas do módulo MFE que se registrou na API register. Se o arquivo responsável pelo registro no agente do navegador for encontrado na assinatura da pilha de chamadas da requisição AJAX que está sendo acionada, esse evento será atribuído ao MFE em vez do contêiner.

Correções de bugs

Replays de sessão não estão funcionando para aplicativo Angular em execução no Safari

Corrige um problema em que os replays de sessão falhavam ao capturar qualquer gravação além de um snapshot inicial para aplicativos Angular em execução no Safari.

Reverter substituidor circular

Observou-se que o método de substituição circular aplicado às operações JSON.stringify causava lentidão em casos de nicho com objetos profundamente complexos e aninhados emitidos em rápida sucessão, como em manipuladores de eventos scroll. Este método foi revertido para uma operação mais rápida e simples para reduzir gargalos de desempenho.

Declaração de apoio

New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem ao fim de sua vida útil. As datas de lançamento refletem a data de publicação original da versão do agente.

Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este dashboard de status para obter mais informações.

De acordo com a nossa política de suporte a navegadores, a v1.312.0 do agente de Browser foi desenvolvida para e testada nestes navegadores e intervalos de versões: Chrome 136-146, Edge 136-146, Safari 18-26 e Firefox 138-148. Para dispositivos móveis, a v1.312.0 foi compilada e testada para Android OS 16 e iOS Safari 18-26.2.

March 20
Browser agent v1.311.0

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

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.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.

February 19
Browser agent v1.310.1

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

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.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.

February 17
Browser agent v1.310.0

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.

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

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.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.

February 3
Browser agent v1.309.0

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

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.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.

January 8
Browser agent v1.308.0

v1.308.0

Recurso

adiciona suporte para tags mfe com a API de registro

Adiciona suporte para adicionar tags de entidade através do uso da API de registro

adiciona atributo child.id para facilitar a interligação MFE

Adiciona um atributo child.id aos dados duplicados para facilitar a interligação futura na interface do usuário

Adicionar API "deregister"

Adiciona suporte para cancelar o registro de uma entidade registrada, para uso com a próxima iniciativa de suporte a Micro Front End.

adiciona atributo parent.type para facilitar a síntese de relacionamento

Adiciona o atributo parent.type necessário para a futura síntese de relacionamento durante a ingestão MFE.

Adicionar motivo de fechamento padrão

Adicione um motivo de fechamento padrão de unknown aos eventos WebSocket cujo motivo de fechamento não pôde ser determinado.

Correções de bugs

aplicar valores não nulos nos campos numéricos

Certifique-se de que os campos numéricos sejam sempre relatados em eventos WebSocket, usando 0 por padrão em vez de undefined

Limpar URLs WebSocket

Remover fragmentos de hash e parâmetros de consulta de URLs relatados em eventos WebSocket

Declaração de apoio

New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem ao fim de sua vida útil. As datas de lançamento refletem a data de publicação original da versão do agente.

Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este dashboard de status para obter mais informações.

Consistente com nossa política de suporte ao navegador, a versão v1.308.0 do agente do Browser foi construída e testada para estes navegadores e intervalos de versões: Chrome 133-143, Edge 133-143, Safari 17-26 e Firefox 136-146. Para dispositivos móveis, a versão v1.308.0 foi construída e testada para Android OS 16 e iOS Safari 17-26.

January 6
Browser agent v1.307.0

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

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.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.

Droits d'auteur © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.