A Small Change to Improve Browsers for Keyboard Navigation

Rarely, I find a page that doesn’t use the document scroll area, but makes its own which is not focused, and so you have to focus that (by Tab as many times as necessary, or by clicking) before you can scroll by keyboard. But that’s rare.

Long ago, Firefox started compensating for sticky headers, reducing the amount it would scroll the page by, and it mostly works well, though it’s not flawless. I don’t think I’ve observed the same feature in other browsers. One amusing situation that can arise is when the header disappears when you go down and reappears when you go up, so that repeating PageUp and PageDown yields net movement in one direction.

—⁂—

¹ End, but not Home, which is Fn+Left on my laptop, but the Left key hasn’t worked for over a year now. I’ve contemplated replacing the battery and keyboard, but the laptop’s falling apart in enough other ways it doesn’t quite feel worth the investment…

    Tab+tab+enter

Now, with the summary, it's:

    Tab+tab+enter+tab+tab

The lenovo keyboard with its trackpoint and mouse buttons is a kind of solution to this, but IME scrolling is still a PITA as it needs two inputs (switching to scroll mode while moving the trackpoint)

Apparently no one else was interested in it. I still use it daily.

Only applies to public and commercial services, though.

ShortCat uses the accessibility API to put Vimium-style keyboard links on buttons and text fields in any app.

I find that Vimium works faster in Firefox than using ShortCat to click around websites, so I use both, but ShortCat technically should do everything (clicking-wise) that Vimium does.

[0] https://tridactyl.xyz/about/

edit: added url

    map gf LinkHints.activateOpenInNewTab count=999999
    map go LinkHints.click direct="focused" mode="newtab-active"
    map gb LinkHints.click direct="focused" mode="newtab"

    map gm toggleMuteTab
    

Share your interesting options.