Obsolete
Status Update
No update yet.
Comments
br...@gmail.com
I'm seeing this issue too.
It's not as simple as 'when dev-tools' is open in my case though. It seems to be related to the mobile test view in the dev tools but I haven't found a bullet-proof repro just yet. Just wanted to let you know there are more of us experiencing this.
It's not as simple as 'when dev-tools' is open in my case though. It seems to be related to the mobile test view in the dev tools but I haven't found a bullet-proof repro just yet. Just wanted to let you know there are more of us experiencing this.
mi...@4horsemen.de
I can confirm this in a similar way: after a while working with dev tools and lots of mouse eventhandling the mousemove suddenly stops working and is not fired anymore.
Just restarting chromium helps so far.
my user agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Just restarting chromium helps so far.
my user agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
la...@google.com
[Empty comment from Monorail migration]
[Monorail components: Blink>JavaScript]
[Monorail components: Blink>JavaScript]
ha...@chromium.org
I don't think this is V8 related. Moving to correct queues.
[Monorail components: -Blink>JavaScript Blink>Events Platform>DevTools]
[Monorail components: -Blink>JavaScript Blink>Events Platform>DevTools]
al...@chromium.org
Repro case would help a lot.
Could that be that the events get lost when DevTools is focused?
Could that be that the events get lost when DevTools is focused?
du...@chromium.org
b4bomsy@ : As said in above comment # 5, could you please help providing a sample jsfiddle/url and the steps involved to reproduce the issue to further investigation.
And as mentioned in the original report,it is an older version of chrome, please upgrade to the latest stable version 49.0.2623.87 and let us know if its still an issue here.
And as mentioned in the original report,it is an older version of chrome, please upgrade to the latest stable version 49.0.2623.87 and let us know if its still an issue here.
ka...@chromium.org
b4bomsy@ could you please respond to above comment and provide us sample URL to triage the issue from test team end.
Thanks,
Thanks,
li...@chromium.org
No repro for test team to triage , updating the label.
dg...@chromium.org
[Empty comment from Monorail migration]
is...@google.com
This issue was migrated from crbug.com/chromium/251729?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Add an eventlistener to handle mouse move events
2. open the console/devtools window
3. move mouse to generate events
What is the expected behavior?
Mousemove Events should be generated on each pixel the mouse is moved, whether the devtools window is open or not.
What went wrong?
The handler for the mousemove event never gets called as long as the console/devtools window is open, but once it is closed it gets called.
Did this work before? Yes On previous versions of chrome
Chrome version: 27.0.1453.110 Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)