Issue metadata
Sign in to add a comment
|
Back and forward buttons on pointing devices result in double actions two backs or two forwards
Reported by
jim.dantin@chromium.org,
Feb 21 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.30.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.65 Safari/537.36 Platform: 10323.30.0 (Official Build) beta-channel auron_yuna Steps to reproduce the problem: 1. Browse the internet by following links between pages 2. Click the hardware 'back' button on an external mouse or trackball 3. notice that you have moved back TWO pages, not one What is the expected behavior? Prior to this release, the back and forward buttons operated as expected. What went wrong? Since this update, both back and forward act like you are clicking twice. Did this work before? Yes Beta 64 Chrome version: 65.0.3325.65 Channel: beta OS Version: 10323.30.0 Flash Version: 28.0.0.161 I have verified this using multiple Logitech M570 wireless trackballs. Also verified by another user with a Bluetooth Logitech MX Anywhere 2 mouse. https://productforums.google.com/forum/#!topic/chromebook-central/fgDWy5_mre4 Chromebook Central TC #CBC-RS/TC-watchlist
,
Feb 23 2018
,
Feb 26 2018
+1 Logitech MX Anywhere 2 mouse via Bluetooth also, Acer Chromebook 11 CB3-111 Version 65.0.3325.89 (Official Build) beta (64-bit) - current latest update. May or may not be connected, but also I seem to lose the ability to mouse-scroll in some tabs, I think the trigger is scrolling before the page has finished loading. Only solution is to copy the URL, close the tab and re-open the URL in a new tab to get the mouse-scroll to work again.
,
Feb 28 2018
To be a bit more specific: I noticed that *pressing* the button results in one action, and then subsequently *releasing* the button triggers the second one. I compared that a device on an older version where only pressing, but not releasing, triggers it.
,
Feb 28 2018
,
Feb 28 2018
I can confirm I am also seeing the issue with mouse-scroll. I have not been able to confirm a pattern for the behavior only that the function is missing in some cases.
,
Mar 6 2018
Confirmed with a Kensington Expert Mouse Wireless Trackball attached to a Pixelbook running Version 66.0.3356.0 (Official Build) dev (64-bit) (Dev Channel)
,
Mar 6 2018
keytoaster@google.com - quite right with the two events being fired... this could probably point to the required patch. I would suggest that the "back" event should only fire on "onmouseup" and not "onmousedown", and that firing on both is a bug.
,
Mar 27 2018
,
Mar 28 2018
Have two CBs. The same problem started after I went from Chrome64 stable to 65 stable.
,
Apr 3 2018
I am responsible for 7 Chromebooks; various models. All 7 of them, with various Bluetooth mice, experience the same issues detailed above. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by eric.sm...@cargotec.com
, Feb 21 2018