-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
f<Shift>x
no longer opens the link at x
in a new tab
#2642
Comments
OS version:
|
I'll look into this. |
Thank you! One more note: the same happens with |
smblott-github
added a commit
to smblott-github/vimium
that referenced
this issue
Sep 14, 2017
Fixes philc#2642.
Merged
smblott-github
added a commit
that referenced
this issue
Sep 14, 2017
smblott-github
added a commit
that referenced
this issue
Sep 14, 2017
This should be fixed in v1.60.1 (which is rolling out to Chrome users now). |
You're the best—thanks so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just upgraded to Vimium 1.60. An important piece of functionality appears to have regressed.
Previously, if I were to press
f
and a link targetABC
were to appear, then I could pressab<Shift-c>
to open the link in a new tab. That is,fab<Shift-c>
behaved in the same way as<Shift-f>abc
.This is no longer the case. Now, pressing
<Shift-x>
for anyx
while inf
-mode deactivatesf
-mode. That is, pressingf<Shift-a>
orfab<Shift-c>
is the same as pressing no key at all.I noticed this behavior on Chrome 60.0.3112.90. I then upgraded to Chrome 61.0.3163.79, which has the same behavior.
(Edited to clarify key notation.)
The text was updated successfully, but these errors were encountered: