Cannot proxy and dispatch mouse event
Reported by
arbesf...@gmail.com,
Sep 29 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: https://jsfiddle.net/asms4hwq/ I create an event listener and then try to dispatch the event with a proxy. What is the expected behavior? I'd expect to be able to re-dispatch the event. What went wrong? I get the error: VM103:46 Uncaught TypeError: Failed to execute 'dispatchEvent' on 'EventTarget': parameter 1 is not of type 'Event'. Did this work before? No Chrome version: 53.0.2785.116 Channel: stable OS Version: OS X 10.11.4 Flash Version: Shockwave Flash 23.0 r0
,
Sep 30 2016
I think this is intentional. Adam, Dan WDYT?
,
Oct 3 2016
This is definitely the expected behavior. One could imagine changing the WebIDL spec to allow proxies for host objects, but it doesn't currently, and until it does, this is the correct behavior.
,
Oct 17 2016
I discussed this with Anne van Kesteren, and he said that it was intentional: Proxies are blocked by WebIDL in all sorts of contexts to shield web spec authors from the ways that they break platform invariants, so the brand checks exist deliberately. |
||||
►
Sign in to add a comment |
||||
Comment 1 by schenney@chromium.org
, Sep 29 2016