One mouse wheel event is ignored when changing the scroll direction on Wayland
Reported by
arnomgob...@gmail.com,
Jun 11 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: 1. Open a webpage in Chromium on Wayland/GNOME-Shell. 2. Scroll downward with the mouse wheel. 3. Scroll upward. What is the expected behavior? The webpage begins to scroll immediately when I push the mouse wheel upward. What went wrong? The first mouse wheel movement is ignored, I have to push the mouse wheel a second time to begin scrolling in the new direction. Did this work before? N/A Chrome version: 59.0.3071.86 Channel: stable OS Version: Flash Version: I'm on Archlinux with GNOME 3.24.2, using Wayland. Chromium is the only application that shows this behavior.
,
Jun 19 2017
,
Jun 19 2017
I'm on Ubuntu GNOME 17.04 now, and having the same issue. GNOME 3.24.2.
,
Jun 22 2017
Tested this issue using latest stable #59.0.3071.109 on Linux Ubuntu 16.04 and was unable to reroduce the issue as per the steps mentioned in original comment. Able to scroll the page downwrds and upwards. Please find the below screen cast for reference. Thanks!!
,
Jun 22 2017
Please note that this happened to me with GNOME Shell 3.24 on a Wayland session. I don't think that you're using either of them in your screencast. Also, the problem is not that I'm unable to scroll in one direction, but that one (and only one) mouse scroll event is ignored when I change direction.
,
Jun 22 2017
This is related to issue 712737 in that mouse wheels in general are pretty busted in Wayland. We had this same issue in X and fixed it in issue 593453 . Unfortunately, the way things are currently we can propertly support either X or Wayland but not both without doing some major work. Input team currently doesn't have the resources to work on this in the short term.
,
Jun 25 2018
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
,
Jun 28 2018
bokan@ do we have any plans to work on this issue?
,
Jul 4
,
Jul 4
Assigning to thomasanderson@ to triage for Linux issues. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Jun 12 2017