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

Issue 693109 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Need to revisit all existing checks for left buttons in dom MouseEvent

Project Member Reported by mustaq@chromium.org, Feb 16 2017

Issue description

We still have some cases that low-level mouse events for a left-drag action is assumed to have button=Button::Left (similar to the UI MouseEvent spec). This is not true for mouse events from Android, which have button=Button::NoButton in such cases (similar to the PointerEvent spec).

We fix-up the JS-visible button value right before dispatching dom events so web is not affected. But internal event plumbing is still affected. E.g. we discovered one such case in MouseEventManager::handleMouseDraggedEvent() while working on  Issue 666060 .

 

Comment 1 by mustaq@chromium.org, Feb 22 2017

Status: WontFix (was: Available)
We have decided to switch Android assumptions to match other platforms. WAI.

Comment 2 by mustaq@chromium.org, Feb 22 2017

For context: crrev.com/2639623002

Sign in to add a comment