W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [DOM3Events] Use cases for Mutation Events

From: Sergey Ilinsky <castonet@yahoo.co.uk>
Date: Thu, 4 Jun 2009 12:44:43 +0000 (GMT)
Message-ID: <943540.41719.qm@web24408.mail.ird.yahoo.com>
To: Joćo Eiras <joaoe@opera.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Webapps WG <public-webapps@w3.org>

> 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.

They do not know now if document is mutated (generally speaking), and the developers who use those libraries got used to that?
Also, if I am not mistaken, Webapps group is here to eliminate the very need in such libraries by standardazing and pushing the consistent API to the browsers world.

> 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.

3rd party libraries should rather provide an API to their functionality, than letting developers to discover effect they caused from the view (HTML/SVG).


Received on Thursday, 4 June 2009 12:45:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:12:54 UTC