Vimium: Vimium binds alt-f, which Chrome 70 now uses

[matthew-cline]

The key combo alt-f is now being using by Chrome 70 to open its main menu. However, vimium grab that key combo first. This mean I have to manually do unmap <a-f> so I can exit the browser with alt-f x, as ctrl-shift-Q no longer exits the browser.

Chrome version: 70.0.3538.67 (Official Build)
Vimium version: 1.64

[friederbluemle]

I also have this issue and would appreciate a fix. :bow:

[pdf]

Duplicates #490 though this is clearly a much more significant problem now.

[innaterebel]

Not a fix but... Alt+E does the same thing with Alt+F, and is much easier to press in my opinion.

I am confused though, this two bindings have always been the shortkeys to open the main menu for Chrome from the beginning, why only now it becomes a prominent trouble? Because the departure of Ctrl+Shift+Q causes people to... uhh, finally has the need to open main menu? :stuck_out_tongue_winking_eye:

[gdh1995]

<a-f> is not managed by Chrome 70 on Windows. That is to say, I can still use <a-f> to trigger LinkHints.activateModeWithQueue.

Are you using Mac OS ?

Update: sorry I misunderstood what you had said.

[milessabin]

There's some discussion of the removal of ctrl-shift-q on this chrome ticket (scroll to the recent comments at the end). I tend to only ever have a single chrome window open, so ctrl-shift-w is an a more or less acceptable substitute for me.

[breyed]

Can Vimium just ignore and pass through keys when Alt is pressed? Doing so might resolve #3360 also.

[gdh1995]

What are your systems which have such a bug?

[breyed]

Google Chrome Version 78.0.3904.97 (Official Build) (64-bit) on Windows 10.
Vimium 1.64.6.

[gdh1995]

@breyed Well, I just notice that Vimium's default key mappings includes map <a-f> LinkHints.activateModeWithQueue, so you may just add a line of unmap <a-f> to "Custom key
mappings" on the Vimium Options page.

[breyed]

@gdh1995 The unmap fixed it. In the ? help page, there's an advanced binding, "a-f Open multiple links in a new tab". Adding the custom key mapping, unmap <a-f> caused Alt+F to open the Chrome menu.

Since Alt+F does logically fit well with the existing f and F commands, one solution is to add to the ? help screen a mapping for Alt+E to the Chrome menu. This would be documenting a Chrome shortcut, not a Vimium shortcut, but they're no harm in that; it's all keys in Chrome to the user. By showing the lesser known Alt+E, the user wouldn't be left thinking that no Chrome menu shortcut was available - especially if the user didn't happen to show the advanced Vimium options.

[gdh1995]

No, in fact Vimium is not allowed to open Chrome's main menu.

So the only thing Vimium may change is to give up its <a-f>.

[breyed]

I'm not suggesting that Vimium open Chrome's main menu, just that it documents the existing <a-e> that Chrome already uses to open its main menu.

To take the concept a step further, you could include all Chrome shortcuts in the Vimium help page. The Vimium help page would be a combination of Vimium and Chrome shortcuts, basically telling the user, "Here's everything you've got to work with." Other than opening the main menu, I don't know what other Chrome commands exist that don't already have Vimium key bindings, but if there are any, it would be nice to know about them.

[innaterebel]

That would be very cumbersome I afraid. In fact Chrome has one of the best native accessibility support among all browsers, its keyboard shortcut list is huge, and is ever evolving.
For example it now even supports moving a tab via keyboard, and is exploring to support selecting multiple tabs and move them at once with keyboard.

Perhaps embed a link to the official support's keyboard shortcut page instead.