New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 715114 link

Starred by 1 user
Status: Assigned
Owner:
mustaq@chromium.org
Cc:
█ aelias@chromium.org
dtapu...@chromium.org
mustaq@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 686196


Sign in to add a comment

Hovering across Android split-screen should fire mouseenter/leave

Project Member Reported by mustaq@chromium.org, Apr 25 2017 
Hovering across the border on Android-N split-screen mode should fire mouseenter/leave events, but currently this doesn't happen.

Test page: http://rbyers.github.io/eventTest.html

We are currently filtering out MotionEvent.ACTION_HOVER_ENTER/EXIT in ContentViewCore.java/EventForwarder.java, and then again mapping mouse-enter/leave events to mouse-moves at the WebMouseEvent level ( Issue 686196 ). We will need to fix both these if hovering across the split actually fires ACTION_HOVER_ENTER/EXIT events.

One tricky thing is that every mouse-down on Android follows a hover-exit and every mouse-up is followed by a hover-enter. The MotionEvent spec seems to support this behavior indirectly.
Project Member

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

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by nzolghadr@chromium.org, Apr 26 2018

Owner: mustaq@chromium.org
Status: Assigned (was: Untriaged)
Mustaq, you mentioned  Issue 686196  that is now fixed. Is it possible to now listen to now not filter MotionEvent.ACTION_HOVER_ENTER/EXIT and just send leave event and move event accordingly.

Comment 3 by mustaq@chromium.org, Apr 26 2018

Labels: -Hotlist-Recharge-Cold -M-58
Sending enter/leave events directly would be a problem because a button click is bracketed by hover-end/-begin events (with an event sequence like [ACTION_HOVER_EXIT, ACTION_DOWN, ACTION_UP, ACTION_HOVER_ENTER]).

The documentation doesn't mention a way to distinguish between two types of hover-exits (hover-out vs button-down):
https://developer.android.com/reference/android/view/MotionEvent.html#ACTION_HOVER_ENTER

Perhaps tracking the coordinates is the only option we have, but it won't be a clean solution.

Comment 4 by acondor@chromium.org, Jun 8 2018 

We have run into this issue in VR browsing. We decided to send a ACTION_HOVER_MOVE with a fixed out-of-bounds point to mimic ACTION_HOVER_EXIT. However, we are not quite sure of the implications of this fixed point. Drag seems to work fine if we keep sending ACTION_MOVE with out-of-bounds points.
►

Sign in to add a comment