domNode.addEventListener in UNA 14.0.0

These functions have long since stopped working on modern browsers but are used in UNA 14.0.0. I don’t understand why UNA 14 should still include code that is not functional for the past year. What is the rationale or justification for UNA 14’s continued inclusion of code that has been non-functional in modern browsers for the past year? Can someone enlighten me?”

Chrome error:

[Deprecation] Listener added for a 'DOMNodeInserted' mutation event. Support for this event type has been removed, and this event will no longer be fired. See for more information.Understand this error

gzip_loader.php?file=bx_templ_js_ccde4f8d24c2357138b4d559b1894ace.js:1435 [Deprecation] Listener added for a 'DOMNodeInserted' mutation event. Support for this event type has been removed, and this event will no longer be fired. See https://chromestatus.com/feature/5083947249172480 for more information.

Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, `DOMNodeRemoved`, `DOMNodeRemovedFromDocument`, `DOMNodeInsertedIntoDocument`, and `DOMCharacterDataModified`, are quite bad for page performance, and also significantly increase the complexity of adding new features to the Web. These APIs were deprecated from the spec (

Spec: UI Events ) in 2011, and were replaced (in 2012) by the much better-behaved Mutation Observer API. Usage of the obsolete Mutation Events must now be migrated to Mutation Observer.

Mutation event support will be disabled by default starting in Chrome 127, around July 30, 2024. Code should be migrated before that date to avoid site breakage. If more time is needed, there are a few options:

- The Mutation Events Deprecation trial (https://developer.chrome.com/origintrials/#/view_trial/919297273937002497) can be used to re-enable the feature for a limited time on a given site. This can be used through Chrome 134, ending March 25, 2025.

- A MutationEventsEnabled enterprise policy (https://chromeenterprise.google/policies/#MutationEventsEnabled) can also be used for the same purpose, also through Chrome 134.

Please see this blog post for more detail:

https://developer.chrome.com/blog/mutation-events-deprecation

Report bugs here: https://issues.chromium.org/new?component=1456718&template=1948649