The W3C DOM MutationObserver API is verbose and unintuitive. This wrapper simply aims to make DOM observation terse and obvious.
// A single function for mutation observation// => MutationObserver// An options object with all boolean flags set to true for broad capturemutyoptions
// Blanket logging of all DOM mutations// In application code, maybe something like thisvar editor = document
- A MutationRecord processor, or any kind of higher-level abstraction. Use Mutation Summary instead.
- A MutationObserver polyfill for non-supporting browsers. Use Mutation Watcher instead.
- A perfect API: