Hi, For me it is not clear at all what are the use cases for DOM Mutations Events on web pages (so maybe simply dropping their implementation would be an option?).
If the group could first identify the use cases for Mutation Events on the web pages, then: a) it would become clear to everyone whether the progress is needed b) creating proposals on progress would become easier, a proposal would have to satisfy these use case to prove its viability Other thoughts: 1) If I am the author to the scripts that modify document, then I am indeed aware of what gets changed. If I am not the author, I shall then not have been notified on the change. The use cases such as "debugger" do not count here - it would be possible to offer required APIs (such as DOM Mutation Events) to them only, without needing the API to populate on the page. And this is not a sucrifice to run page 50% slower caused by the Mutation Events turned on on behalf of a debugger, right? 2) I can see Mutation Events as the extension point that enables implementation of the technologies that are not available in the browser. However this is not a "normal" usecase that web browsers are here to face. Sergey/
