- From: Dave Tapuska <notifications@github.com>
- Date: Tue, 21 Feb 2017 06:01:22 -0800
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 February 2017 14:02:36 UTC
Since initUIEvent probably isn't going away anytime soon. It should be clearly documented with respect to its arguments instead of its current specification of no arguments. It is present in multiple browsers according to MDN; https://developer.mozilla.org/en-US/docs/Web/API/UIEvent/initUIEvent We need to decide what the actual specified behavior is: Chromium has this: void initUIEvent([Default=Undefined] optional DOMString type, [Default=Undefined] optional boolean bubbles, [Default=Undefined] optional boolean cancelable, [Default=Undefined] optional Window? view, [Default=Undefined] optional long detail); But it identifies that all the values should not be optional. We need to figure out what other vendors have. @garykac @foolip @smaug---- -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/133
Received on Tuesday, 21 February 2017 14:02:36 UTC