(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? * `MOZ_USE_XINPUT2=1` does not seem to change behavior. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR tio be "on wayland", i.e. start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.
Bug 1748921 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? * `MOZ_USE_XINPUT2=1` does not seem to change behavior for me. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR tio be "on wayland", i.e. start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? * `MOZ_USE_XINPUT2=1` does not seem to change behavior for me. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR to actually be "on wayland", i.e. if I start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? Details below, but briefly: I think my Firefox session is in X11 mode, and MOZ_USE_XINPUT2 doesn't change anything AFAICT; and if I use wayland-mode, then I get a new and different behavior (scrolling slightly less far but still pretty far). * `MOZ_USE_XINPUT2=1` does not seem to change behavior for me. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR to actually be "on wayland", i.e. if I start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? Details below, but briefly: I think my Firefox session is in X11 mode, and MOZ_USE_XINPUT2 doesn't change anything AFAICT; and if I use wayland-mode, then I get a new and different behavior (scrolling slightly less far but still pretty far). More details: * `MOZ_USE_XINPUT2=1` does not seem to change behavior for me. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR to actually be "on wayland", i.e. if I start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > That's fairly concerning. I haven't seen this generally, but two things: > > * Does `mousewheel.system_scroll_override.enabled` change this? Yes, it does! If I toggle that to `false`, then the STR only get me halfway down the page (which matches Chrome's behavior). > * Is this on wayland (`MOZ_ENABLE_WAYLAND=1`) or X11? if on X11, does `MOZ_USE_XINPUT2=1` help / change behavior? Details below, but briefly: I think my Firefox session is in X11 mode, and MOZ_USE_XINPUT2 doesn't change anything AFAICT; and if I opt in to using Firefox in wayland mode, then I get a new and different behavior (scrolling slightly less far but still pretty far). More details: * `MOZ_USE_XINPUT2=1` does not seem to change behavior for me. (If I start Firefox with `MOZ_USE_XINPUT2=1 firefox`, my touchpad-swipe still scrolls the full height of the page, or half the height of the page if I toggle the aforementioned mousewheel pref.) * I am using Wayland at an OS level (i.e. `echo $XDG_SESSION_TYPE` prints `wayland`, and I do see `Window Protocol xwayland` in `about:support`). * ...however, I do not have the `MOZ_ENABLE_WAYLAND` environmental variable explicitly set, which I think means my answer is "no, not on wayland" for the purposes of your question. * If I adjust my STR to actually be "on wayland", i.e. if I start Firefox with `MOZ_ENABLE_WAYLAND=1 firefox`, **then** a full-touchpad-swipe takes me ~80% of the way down the page (intermediate between the Chrome results, and the stock-Firefox results, which take me ~50%/100%). Also, the `mousewheel.system_scroll_override.enabled` pref seems to stop making a difference (no change in results when I toggle that pref) under this opted-in-to-wayland configuration.