33861 2010-01-19 13:19:51 -0800 Document is not notified about event listener changes 2026-03-26 06:05:15 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All All RESOLVED INVALID P2 Major --- 1 zimmermann webkit-unassigned ap cdumez darin ddkilzer eric mjs staikos tonikitoo oldest_to_newest 182410 0 zimmermann 2010-01-19 13:19:51 -0800 Document keeps track wheter a certain event listener is available in the DOM, we only dispatch certain events if document()->hasListenerType(..) returns true. In Node::addEventListener, we're adding the listener type, but in Node::removeEventListener we're not notifying the Document that something changed. We need to switch to a counting based tracking scheme, counting how many event listeners are registered for each event type. This bug can introduce performance problems, when adding a mutation event listener once for ie. <body> and then removing it. We will never stop dispatching mutation events. 706434 1 ap 2012-08-28 09:45:32 -0700 Does this happen on real web sites? Counting listeners would add a toll on every web site, while benefits seem unlikely to materialize. 1502834 2 lforschler 2019-02-06 09:02:44 -0800 Mass moving XML DOM bugs to the "DOM" Component. 2193911 3 zimmermann 2026-03-26 06:05:15 -0700 Mutation events are no longer relevant.