New issue
Advanced search Search tips

Issue 746762 link

Starred by 1 user
Status: WontFix
Owner:
ccameron@chromium.org
Closed: Jul 2017
Cc:
ccameron@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

mousemove event is not fired on blurred chrome window on MacOSX only

Project Member Reported by zijiehe@chromium.org, Jul 20 2017 
Chrome Version: (copy from chrome://version)

Version 60.0.3112.10 (Official Build) dev (64-bit) on Ubuntu 14.04.2
Version 61.0.3117.0 (Official Build) canary (64-bit) on Mac OSX 10.12.5
Version 61.0.3159.0 (Official Build) canary (64-bit) on Windows 10

What steps will reproduce the problem?
(1) Open https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_onmousemove or any other similar web pages to listen "mousemove" event.
(2) Let the browser window blurs, for example, open a notepad.
(3) Do not let the newly opened window to cover the page.
(4) Move the mouse cursor in the test area on the page. But do not let browser window take focus.

What is the expected result?
The behavior should be consistent on different platforms.

What happens instead?
The page cannot receive "mousemove" event on MacOSX only.

Comment 1 by dtapu...@chromium.org, Jul 20 2017

Cc: ccameron@chromium.org
I believe this is done on purpose. This is traditionally the way the window manager works on MacOSX and is consistent with Safari.

ccameron@ do you agree?

zijiehe@ is this causing you specific issues? Or are you just surprised of the platform differences?

Comment 2 by dtapu...@chromium.org, Jul 20 2017

Labels: Needs-Feedback

Comment 3 by zijiehe@chromium.org, Jul 20 2017 

No, I just randomly found the difference.

Comment 4 by ccameron@chromium.org, Jul 21 2017

Owner: ccameron@chromium.org
Status: WontFix (was: Untriaged)
It's good to know -- matching Safari on UI behaviors like this is the right thing to do, to feel more like a Mac application.
►

Sign in to add a comment