Should mouse boundary events fire on Mac/ChromeOS when cursor hidden |
||
Issue descriptionWhen pressing keyboard events on Mac/ChromeOS the keyboard hides the mouse cursor yet we still fire boundary events at the last position of the mouse. Wonder if we shouldn't fire anything in these cases. ie; should we reset the mouse cursor to a position unknown on mouse leave?
,
Oct 24 2017
Ah yes you are correct; we don't send the mouse leave for interop purposes. But what is weird is we update the hover state of pages that lay out and it shows what the last hovered node is.
,
Oct 24 2017
So yeah. I'm totally up for matching current hover state update and also send the boundary events in favor of consistency and predictability. I'm not sure what the breakage will be in that case though. Marginally related, that we also remove hover state on mac when mouse opens the context menu which I'm again in favor. But I recall some people were complaining about.
,
Oct 26 2017
Closing as this is a can of interop worms and there is no immediate need. |
||
►
Sign in to add a comment |
||
Comment 1 by nzolghadr@chromium.org
, Oct 24 2017