DOM Mutation Events are a problem

[avoidwork]

This is not the ideal way to 'unhook' a potentially destroyed Element from the Observer; 3.6.11 is a stop gap to something better, but that something better needs to be finalized & implemented.

The root problem is a copy/paste into an input field triggers an 'input' event, which cascades to a DOMNodeRemoved event, which is factual, but also misleading. Delaying the 'unhook' from the Observer could lead to a false-positive case where something is actually destroyed and re-created with the same ID intentionally, leaving the new Element without the Observer hook.