Status Update
Comments
aj...@google.com <aj...@google.com> #2
Tram, can you confirm that the behavior is correct if the modifier is moved to the composable inside the AnimatedPane?
ja...@gmail.com <ja...@gmail.com> #3
Hi Max, yes when the modifiers are moved to the composable inside the AnimatedPane, the PB animations are better than when the modifiers are in the AnimatedPane itself
ss...@google.com <ss...@google.com> #5
After some investigation, I can conclude this behavior is consistent with other animation "wrapper" composables, e.g. AnimatedVisibility
. Modifiers should indeed be applied to the children in order to properly participate in the animation.
ja...@gmail.com <ja...@gmail.com> #6
>>> Issue seems to related to fedora 41 device specific
To see if this was the case, I setup a virtual environment.
Host is Windows 11 24H2, using VirtualBox 7.1.6 with a fresh installation of Ubuntu 22.04.5 and Chrome 134.
I am able to reproduce the same behavior as I saw on Fedora 41, which is installed directly on a host computer.
My mouse comes through VirtualBox as a generic USB tablet:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Using the scroll wheel generates the following events (via evtest):
Event: time 1741239372.196139, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239372.196139, -------------- SYN_REPORT ------------
Event: time 1741239373.823193, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239373.823193, -------------- SYN_REPORT ------------
Event: time 1741239374.845457, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239374.845457, -------------- SYN_REPORT ------------
Event: time 1741239375.969274, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239375.969274, -------------- SYN_REPORT ------------
Event: time 1741239376.264228, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239376.264228, -------------- SYN_REPORT ------------
Event: time 1741239376.917313, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239376.917313, -------------- SYN_REPORT ------------
Event: time 1741239377.298297, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239377.298297, -------------- SYN_REPORT ------------
With "value 1" being scrolling down and "value -1" being scrolling up.
As with before:
* Scrolling with movement works out of the box with GNOME document viewer.
* Scrolling with movement DOES NOT work out of the box with Chrome.
* Scrolling with movement DOES work after forcing the ozone setting to Wayland.
Screen recordings of this behavior being replicated on an Ubuntu virtual machine are attached.
To see if this was the case, I setup a virtual environment.
Host is Windows 11 24H2, using VirtualBox 7.1.6 with a fresh installation of Ubuntu 22.04.5 and Chrome 134.
I am able to reproduce the same behavior as I saw on Fedora 41, which is installed directly on a host computer.
My mouse comes through VirtualBox as a generic USB tablet:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Using the scroll wheel generates the following events (via evtest):
Event: time 1741239372.196139, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239372.196139, -------------- SYN_REPORT ------------
Event: time 1741239373.823193, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239373.823193, -------------- SYN_REPORT ------------
Event: time 1741239374.845457, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239374.845457, -------------- SYN_REPORT ------------
Event: time 1741239375.969274, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239375.969274, -------------- SYN_REPORT ------------
Event: time 1741239376.264228, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239376.264228, -------------- SYN_REPORT ------------
Event: time 1741239376.917313, type 2 (EV_REL), code 8 (REL_WHEEL), value -1
Event: time 1741239376.917313, -------------- SYN_REPORT ------------
Event: time 1741239377.298297, type 2 (EV_REL), code 8 (REL_WHEEL), value 1
Event: time 1741239377.298297, -------------- SYN_REPORT ------------
With "value 1" being scrolling down and "value -1" being scrolling up.
As with before:
* Scrolling with movement works out of the box with GNOME document viewer.
* Scrolling with movement DOES NOT work out of the box with Chrome.
* Scrolling with movement DOES work after forcing the ozone setting to Wayland.
Screen recordings of this behavior being replicated on an Ubuntu virtual machine are attached.
Description
Steps to reproduce the problem
Problem Description
If there is any mouse movement while trying to scroll, even if it's a small movement, scrolling has a chance to be ignored.
This impacts google chrome under Linux but does not impact Windows.
This was tested in a fresh Fedora 41 Workstation installation, with a fresh installation of google chrome.
Additionally, in the same environment, scrolling while moving the mouse was confirmed to work as expected in both ptyxis and gnome-document-viewer.
Additional Comments
I have included screen recordings of the scrolling behavior in gnome-document-viewer, which shows it working when the cursor is held steady as well as when the cursor is moving.
The second screen recording shows google chrome scrolling when the cursor does not move, but does not scroll if the cursor is moving (I was continuously scrolling while moving), and once again scrolling works if I stop moving the mouse.
Summary
Scroll wheel does not function while moving mouse
Custom Questions
Please select a label to classify your issue:
Type-Bug - Software not working correctly
Additional Data
Category: Other
Chrome Channel: Stable
Regression: N/A