extensions.VimFx.scroll.*_boost do nothing on Linux/Wayland

[TinfoilSubmarine]

I'm having issues with getting this extension fine-tuned for scrolling, but specifically on Linux. I say this because I also installed this on a Windows machine and have no issues adjusting scrolling there.

However, on Linux, when I adjust these settings, it doesn't change anything. I'd be happy to dig into logs, advanced settings, etc. I just don't know where to start.

[TinfoilSubmarine]

Oh great.

I just had a hunch and ran Firefox under Xorg and it works fine, while both Sway (Wayland) and GNOME on Wayland exhibit this issue.

[girst]

On Wed, Aug 24, 2022 at 07:44:14AM -0700, Joel Beckmeyer wrote: Oh great. I just had a hunch and ran Firefox under Xorg and it works fine, while both Sway (Wayland) and GNOME on Wayland exhibit this issue.

interesting. i never changed those prefs myself, so i had a quick grep though the code. it looks like they are used by extension/lib/commands.coffe, in helper_scrollByLinesY (and X), where they are multiplied by the scroll amount. helper_scoll (same file) does some more magic and (through viewportUtils.scroll) hands off to the native method Element.scrollBy(). the call will end up something like document.documentElement.scrollBy({top: 100, left: 0, behaviour:'smooth'}) i have no clue what causes your issue, so i'm afraid i can't be of any help. if you do get to the bottom of this, i'd appreciate an update though :) i can't see how that behaviour depends on the windowing system, but maybe you're dealing with a firefox bug here?

[girst]

one more thing: it's unlikely to be helpful in this case, but in general, you should look at the browser console (not the web developer console) for logs. you can reach it with ctrl+alt+j. if you enable "browser chrome and add-on debugging toolboxes" and "remote debugging" from the devtools (hit f12, then f1 to go to the settings, scroll down to the end), you can even execute javascript snippets in the browser's privileged scope/context.

[TinfoilSubmarine]

I just noticed something interesting:

• On Xorg, by default, scrolling with arrow keys matches the speed of scrolling with hjkl.
• On wayland, by default, scrolling with arrow keys is faster than scrolling with hjkl.

Maybe there is some other layer here that is getting added/modified by Firefox's Wayland backend? The weird thing is, I already saw on ArchWiki that there is something weird with kinetic scrolling on Wayland, but disabling (apz.gtk.kinetic_scroll.enabled set to false) didn't fix...

[TinfoilSubmarine]

I just noticed something interesting:

* On Xorg, by default, scrolling with arrow keys matches the speed of scrolling with hjkl.

* On wayland, by default, scrolling with arrow keys is _faster_ than scrolling with hjkl.

Maybe there is some other layer here that is getting added/modified by Firefox's Wayland backend? The weird thing is, I already saw on ArchWiki that there is something weird with kinetic scrolling on Wayland, but disabling (apz.gtk.kinetic_scroll.enabled set to false) didn't fix...

After playing with it for a little bit more, it seems like this is an issue not with scroll distance, but with the repeat delay between scrolling.

I discovered toolkit.scrollbox.verticalScrollDistance which does cause a difference and is what I'll be using to fix the observed slow scrolling under Wayland from my last comment--at least until I can figure out what is causing the discrepancy in the first place.