- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 06 Apr 2018 05:44:00 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 April 2018 12:44:23 UTC
Some issues with `window.event`: * Chrome has (non-standard) [NotEnumerable] in IDL meaning `Object.getOwnPropertyDescriptor()` returns the wrong thing there. Is that something that can be removed by Chrome or do we need it in the standard? * It's a little bit unclear where the global is gotten from. I thought it was related to the target/currentTarget, but https://cs.chromium.org/chromium/src/third_party/WebKit/Source/bindings/core/v8/V8AbstractEventListener.cpp?q=V8AbstractEventListener::InvokeEventHandler&sq=package:chromium&l=135 suggests it's global state. Does that correspond to the "current global object" concept or is it something else? From the test cases I assumed it was somehow related to currentTarget, since if you move nodes in the path between documents you can get the global whose `.event` is set to change as well. But maybe that's just how callbacks work and I'm a little confused. -- 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-379241767
Received on Friday, 6 April 2018 12:44:23 UTC