81564 2012-03-19 14:28:53 -0700 Events do not propagate in disconnected DOM trees 2022-10-23 12:23:42 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 arv webkit-unassigned adamk ahmad.saleem792 annevk ap cdumez ddkilzer dglazkov jwalden+bwo zalan oldest_to_newest 582251 0 arv 2012-03-19 14:28:53 -0700 Given a disconnected DOM tree, we should still do the event propagation. var parent = document.createElement('div'); var child = document.createElement('div'); parent.addEventListener('foo', function(e) { alert(e)}, true); var event = document.createEvent('Event'); event.initEvent('foo', true, true); parent.appendChild(child); child.dispatchEvent(event) Opera and FIrefox both alert here. 582276 1 adamk 2012-03-19 14:45:46 -0700 This seems to be due to the inDocument() check at the top of EventDispatcher::ensureEventAncestors: http://trac.webkit.org/browser/trunk/Source/WebCore/dom/EventDispatcher.cpp#L235 It's been around a long time, dating back to when event dispatch was still in Node.cpp. 582350 2 ap 2012-03-19 15:47:03 -0700 What does IE do? If IE and WebKit agree, it would take much more than just Firefox and Opera opinion to make this change necessary. 837664 3 ap 2013-02-20 12:55:53 -0800 *** Bug 110353 has been marked as a duplicate of this bug. *** 864186 4 arv 2013-03-26 19:31:25 -0700 (In reply to comment #2) > What does IE do? If IE and WebKit agree, it would take much more than just Firefox and Opera opinion to make this change necessary. IE passes the test in bug 110353. This makes WebKit the odd man out. 864196 5 ap 2013-03-26 20:19:03 -0700 *** Bug 113336 has been marked as a duplicate of this bug. *** 872058 6 ddkilzer 2013-04-09 13:43:53 -0700 *** Bug 114023 has been marked as a duplicate of this bug. *** 872059 7 ddkilzer 2013-04-09 13:44:37 -0700 <rdar://problem/13178101> 1502842 8 lforschler 2019-02-06 09:02:47 -0800 Mass moving XML DOM bugs to the "DOM" Component. 1907580 9 ahmad.saleem792 2022-10-22 14:37:42 -0700 Chrome / Blink fixed this in following commit - https://src.chromium.org/viewvc/blink?view=revision&revision=198153 1907673 10 ap 2022-10-23 12:23:42 -0700 We must have fixed this at some point too, the test passes in Safari 16.