vimium scroll down/up do not work properly on ansible documentation site

[vbaruh]

Hi there,

I'm using vimium 1.64 with Google Chrome Stable (version 69) on xubuntu 18.

When you open https://docs.ansible.com/ansible/latest/index.html scroll down and up (j and k) do not work.
If you click in the right-side frame this problem disappears, but it is very annoying.

Note that with Vimium-FF scroll up and down do not work even after you click in the right frame.

Thanks,
Vitali

[smblott-github]

Confirmed.

As a workaround, you can use link hints to select the link labelled D, here:

[alon-to]

@smblott-github: great suggestion! Selecting the relevant 'Scroll' hint works best and most consistently (for example: cycling through gf never brings focus to the right frame in Ansible).

The Scroll label only appears when the "Use the link's name and characters for link-hint filtering" option (aka as Filtered Hints) is enabled, as confirmed here. In fact many labels become active when this feature is enabled as can be seen in screenshot below, and it appears links can be activated in at least three different ways:

1. Typing the hint ID (26 in the screenshot below)
2. Typing the hint label (open in the screenshot below, then scrolling or selecting the new ID)
3. Typing the text in the underlying element (watch in the case of the button under 26)

I'd love for there to be a way to see the Scroll label when Filtered Hints are disabled. There are some UX challenges to work through here but I think it would add a ton of clarity for this particular user journey!

[alon-to]

I just updated and clarified the feature request but not sure if that triggers a notification of any kind so replying to own last message here. I love Vimium!! Thanks so much for building such an amazing tool.

[ntd]

... cycling through gf never brings focus to the right frame in Ansible

This is because it is not a frame: it is a normal <div>. And the left side is a navigational <div> element with overflow-y: scroll.

Not sure what is going on: some websites done in a similar way, such as the SilverStripe 4 API reference or all readthedocs based ones, work just fine.

[anthropikos]

Confirmed.

As a workaround, you can use link hints to select the link labelled D, here:

@vbaruh What is resulting in my filtered-hint not showing the scroll bar being detected?

[gdh1995]

@aoot In Vimium, currently only clicking an element (via LinkHints.activate or a real mouse) can notify Vimium it's scrollable, although this notifying can be easily imported into LinkHints.activateMode with action=hover (which means to "select" an element without clicking).

I have a customized version of Vimium, named Vimium C (https://github.com/gdh1995/vimium-c), and it have such features:

1. Its LinkHints.activateHover will auto mark an element (or an outer element) scrollable, and then j and k work.
2. Render hint markers for scrollable areas in dark red

• 1. an edge case is, when a scrollable area is also "clickable", its marker won't be dark red, but this should have little impact