Need a way to know when ForwardMouseEvent, ForwardKeyboardEvent, and ForwardWheelEvent complete
Reported by
k...@kirkouimet.com,
Jul 1 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: Electron (http://electron.atom.io/) is a popular open source project based on Chromium. One of the functions that Electron exposes is the ability to send input events to the document. This is quite useful and enables some opportunities for automated testing and simulating of events: https://github.com/electron/electron/blob/master/docs/api/web-contents.md#webcontentssendinputeventevent Unfortunately, the underlying Chromium functions that Electron uses for this functionality are asynchronous and do not provide a way to know when they have completed. This makes it impossible to send multiple events in succession or have any guarantee they will arrive in order. I believe the underlying functions are: ForwardMouseEvent ForwardKeyboardEvent ForwardWheelEvent See https://github.com/electron/electron/blob/7d38384bddb5eda16dce945edfbd5c3081646df0/atom/browser/api/atom_api_web_contents.cc#L1150-L1182 for the reference implementation. Is there any way for me to update this code such that I will know when the event has been fully processed? Here is my related issue on the Electron project: https://github.com/electron/electron/issues/6291 Thanks! What is the expected behavior? What went wrong? Currently Chromium offers no ability to know when these events have completed: ForwardMouseEvent ForwardKeyboardEvent ForwardWheelEvent Did this work before? N/A Chrome version: 51.0.2704.103 Channel: n/a OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 22.0 r0
,
Jul 3 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by ccameron@chromium.org
, Jul 1 2016