I'm not sure if it is related to the fresh version or to my recent Chrome reinstall, but currently I've got "F" and "a-f" hotkeys acting exactly like normal "f", that is they open selected link in the current tab.
I use Chrome v 21.0.1180.89 on Debian squeeze.
I have this problem too
21.0.1180.89 (154005) on OpenBSD
I don't have this problem. 21.0.1180.89 on a Mac OS X 10.7.4
It turned out that I have this problem in Windows 7 either. So it seems to be not so OS dependant.
The funny thing is,
I have not this problem on my debian 21.0.1180.89 Debian wheezy/sid (154005),
but have this problem on openbsd 21.0.1180.89 (154005),
and I tried to remove(rm -rf) ~/.config/chromium on openbsd,
then only install vimium by default setting,
but still have this problem.
Any idea to find out what's go on?
Shift-f also not work correct, it open link with current tab, not new tab.
Please help, thank you.
Hi, I want download the old version(<1.37) for testing,
where can I download the binary files?
I have this problem too, on a Mac OS X 10.7.5. :/
Edit : It works, if instead of typing F or f, I type the letters that follows either capital or minuscule.
Hi guys, could you go here, press f and <a-f>, and copy-paste your result here? Remember to disable Vimium and copy with the mouse (otherwise the keypress data will get overwritten).
Hmm, that doesn't look out of the ordinary. Actually, I'm beginning to suspect that this is the same issue as #657, which I've just fixed. Do you mind trying out a copy of the development version (by cloning the master branch) and seeing if the problem has been resolved?
@johnwchrome all past versions are available here: https://github.com/philc/vimium/downloads
I found out what break the "F, O, <a-f>" feature.
I have --user-agent parameter, then I remove it, those feature work as expect now.
Huh, that sounds really strange, but I'm glad you managed to triage it. I'm going to close this in the hopes that either your parameter change or the changes in the latest version will fix it for the rest of the commenters in this thread. Feel free to reopen if the issue still occurs.