- From: Shiino Yuki <notifications@github.com>
- Date: Fri, 06 Apr 2018 15:10:52 +0000 (UTC)
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 April 2018 15:11:23 UTC
For [NotEnumerable] for window.event, I have no evidence, but I guess that `window.event` was not standardized, so Blink didn't want to list up the property in case of enumeration, i.e. Blink wanted to make it a kind of a hidden property because the spec expected Blink to not have window.event. I think that we can remove [NotEnumerable] as window.event is now spec'ed. For which global object Blink is using, I'm not 100% sure, but it looks like Blink is using the global object associated with the EventTarget. I tried to track down where the global object comes from, and reached here: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/events/EventTarget.cpp?rcl=8f0f9ceb2c3f5acf36ef55d620d3f0e6ea7d8d01&l=748 My code reading could be wrong, but I guess that Blink uses the EventTarget => its Document (or Worker) => its Window (or Worker). For node movement during event dispatch, I know nothing, but I think that it's possible that the behavior was implemented without deep thoughts. Maybe Blink should fix it, too. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/334#issuecomment-379283794
Received on Friday, 6 April 2018 15:11:23 UTC