23095 2013-08-30 00:02:37 +0000 "Call listener's callback's handleEvent, with th..." 2014-02-12 19:47:59 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED WORKSFORME P2 normal --- 1 ian annevk bugs dglazkov ian mike morrita www-dom public-webapps-bugzilla oldest_to_newest 92720 0 ian 2013-08-30 00:02:37 +0000 http://dom.spec.whatwg.org/#dispatching-events When invoking event listeners: [[ Call listener's callback's handleEvent, with the event passed to this algorithm as the first argument and event's currentTarget attribute value as callback this value. ]] We should probably not do this if the event handler's Document is not an active document, right? Does that belong in DOM? 92721 1 ian 2013-08-30 00:03:08 +0000 (We should probably test what browsers do.) 92730 2 dglazkov 2013-08-30 04:05:47 +0000 This might be of interest to you: https://groups.google.com/a/chromium.org/d/topic/blink-dev/QHnejis4Yv4/discussion Also, Morrita-san is landing this right now in Blink. 92731 3 bugs 2013-08-30 10:15:59 +0000 Dispatching events doesn't depend on whether or not the document is active or data document. Also just dispatching events in a disconnected subtree should work. In Gecko event listeners do work, but event handlers in data documents aren't registered. 92732 4 annevk 2013-08-30 10:38:00 +0000 Dimitri, that's not about document being active, but about whether it has an associated browsing context. I think what Olli says is correct, though creating test cases for inactive documents is hard. That's basically only documents you have navigated away from, right? 92733 5 bugs 2013-08-30 10:45:22 +0000 Oh, active still... so Gecko doesn't end up calling listeners or handlers on a document which isn't "active", for example is in bfcache. 92734 6 bugs 2013-08-30 10:46:27 +0000 But I've always thought that is an implementation limitation, a bug, in Gecko.