- From: Charles McCathieNevile <chaals@opera.com>
- Date: Sun, 07 Jun 2009 18:11:12 +0200
- To: "Sergey Ilinsky" <castonet@yahoo.co.uk>, "Webapps WG" <public-webapps@w3.org>
Hi, just a reminder that DOM3 discussion should be on the www-dom list. Please follow up there. (I have forwarded the thread, more or less gathered together, to that list.) cheers Chaals On Thu, 04 Jun 2009 12:52:39 +0200, Sergey Ilinsky <castonet@yahoo.co.uk> wrote: > > 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/ > > > -- Charles McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg lærer norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Sunday, 7 June 2009 16:11:52 UTC