New issue
Advanced search Search tips

Issue 835734 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

mousemove event cannot be fired by Input.dispatchMouseEvent interface

Reported by zhenjun....@gmail.com, Apr 23 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. In my extension, I attached to chrome.debugger 1.3
2. And at some point, try to fire mousemove event by:
        var options = {button:"none",
               clickCount: 0,
               type: "mouseMoved",
               x: parseFloat(x),
               y: parseFloat(y)};
        chrome.debugger.sendCommand({tabId: tab_id}, 'Input.dispatchMouseEvent', options);
3. With upper codes, mousemove is not filed, mouseover is filed.

What is the expected behavior?
mousemove event is fired.

What went wrong?
mousemove is not fired

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: n/a
OS Version: Ubuntu 16.04
Flash Version:
 
Labels: Needs-Triage-M65
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please attach a sample/test extension file which helps us to triage the issue in a better way. Any further inputs from your end may be helpful.
@vamshi.kommuri, I did more verification on this, I found this issue is due to long interval(>2 seconds) between two mouseMoved command in my code, it works well if set the interval to 200ms, sorry for bother, you may close this issue, thanks!
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 25 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -OS-Linux
Status: WontFix (was: Unconfirmed)
As per comment#3 by reporter the issue seems to be resolved, hence closing the issue and marking it as Won't fix.

Thanks!
Labels: OS-Linux

Sign in to add a comment