dom / latest / mutationevent.html /

MutationEvent

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Note: Mutation Events (W3C DOM Level 3 Events) have been deprecated in favor of Mutation Observers (W3C DOM4).

The MutationEvent interface provides event properties that are specific to modifications to the Document Object Model (DOM) hierarchy and nodes.

Event MutationEvent

Preface

The mutation events have been marked as deprecated in the DOM Events specification, as the API's design is flawed (see details in the "DOM Mutation Events Replacement: The Story So Far / Existing Points of Consensus" post to public-webapps).

Mutation Observers have replaced mutation events in DOM4. They have been supported in most popular browsers for some years.

In addition, mutation events should be avoided because they have performance issues and poor cross-browser support (as described in the following sections).

Performance

Adding DOM mutation listeners to a document profoundly degrades the performance of further DOM modifications to that document (making them 1.5 - 7 times slower!). Moreover, removing the listeners does not reverse the damage.

The performance effect is limited to the documents that have the mutation event listeners.

Cross-browser support

These events are not implemented consistently across different browsers, for example:

  • IE prior to version 9 didn't support the mutation events at all and does not implement some of them correctly in version 9 (for example, DOMNodeInserted)
  • WebKit doesn't support DOMAttrModified (see webkit bug 8191 and the workaround)
  • "mutation name events", i.e. DOMElementNameChanged and DOMAttributeNameChanged are not supported in Firefox (as of version 11), and probably in other browsers as well.
  • ...

Dottoro documents browser support for mutation events.

Mutation events list

The following is a list of all mutation events, as defined in DOM Level 3 Events specification:

  • DOMAttrModified
  • DOMAttributeNameChanged
  • DOMCharacterDataModified
  • DOMElementNameChanged
  • DOMNodeInserted
  • DOMNodeInsertedIntoDocument
  • DOMNodeRemoved
  • DOMNodeRemovedFromDocument
  • DOMSubtreeModified

Usage

You can register a listener for mutation events using EventTarget.addEventListener() as follows:

element.addEventListener("DOMNodeInserted", function (event) {
  // ...
}, false);

The event object is passed to the listener in a MutationEvent (see its definition in the specification) for most events, and MutationNameEvent for DOMAttributeNameChanged and DOMElementNameChanged.

Browser compatibility

Desktop Mobile
Chrome Edge Firefox Internet Explorer Opera Safari WebView Android Chrome Android Firefox for Android Opera Android Safari on IOS Samsung Internet
MutationEvent
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
attrChange
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
attrName
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
initMutationEvent
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
newValue
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
prevValue
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0
relatedNode
1
12
1
9
≤12.1
1
1
18
4
≤12.1
1
1.0

See also

© 2005–2021 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/MutationEvent