[Webkit-unassigned] [Bug 8191] DOMAttrModified mutation event support
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 5 12:05:56 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=8191
John-David Dalton <john.david.dalton at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |john.david.dalton at gmail.com
--- Comment #18 from John-David Dalton <john.david.dalton at gmail.com> 2009-11-05 12:05:52 PDT ---
I would like to add that mutation events are great if you use them properly.
NWMatcher (a JavaScript CSS Selector engine) has no problems with them. View my
fork here http://github.com/jdalton/nwmatcher/raw/master/src/nwmatcher.js.
1) Avoid compatibility issues through feature detection.
2) Avoid the `slow down` by removing the mutation event listener the first time
it fires and set it up again on subsequent calls.
3) Detect if you are in an abusive while-loop and temporarily pause setting
mutation events.
With proper feature detection mutation events give NWMatcher a boost by
allowing it to cache dom results under certain situations.
Just because something is buggy doesn't mean it should be ripped-out/abandoned.
Currently by viewing nwmatcher.js you will find it covers a lot of bugs in
querySelectorAll(). This does not mean that continued support for
querySelectorAll() should be dropped.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list