Use cases:
- user triggered input, like when using contentEditable/designMode
We should fix this by adding better events for user input into
contentEditable/designMode. Using mutation events for this is both
unnecessarily hard to use (I'd imagine), as well as unperformant (for
sure).
I agree 100% that we need better events for user input in this regard, but we
don't have them currently and Gecko and Webkit dispatch mutation events for
user input on editable documents, and I know of a few high profile project that
use them (although I can't disclose which).
Can you explain these more in detail?
Whether there are libraries that use them or not, I honestly can't tell.
However there are scenarios where 3rd party libraries like jQuery or prototype
might require to know if the document has mutated to update their internal data
structures.
For the 3rd party scripts, it's quite common for sites to deploy 3rd party
scripts that embed links to social networking sites, bookmarking services,
embedding ads, embedding videos, etc. If somehow the script breaks the main
page's tree, a mutation event could help, although in these cases, probably the
load events would be good enough.
