-
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
[Bug] using F opens links twice on Firefox Nightly #3964
Comments
I also noticed this days ago. |
im on nightly too |
https://github.com/gdh1995/vimium-c does not have this problem though a weird thing is that when i disable vimium-ff and then install vimium-c, the vimium-c will have the same problem but it is fixed after i restart firefox (only tested once so may not be reproducible) |
@Artturin Vimium C uses a trick which is not safe on a loaded page, so it only enables this trick if it runs when a page begins loading. If you want to test Vimium C again, please refresh tabs after you enable it and before tests. |
I am using firefox 96.0b2 dev edition, have same problem |
Also experiencing this on 96.0b2 developer edition. |
Also experiencing this issue in Firefox developer edition 96.0b4 version. |
Experiencing the issue on Firefox Nightly 97.0a1 |
This has also been happening in beta for a long time. Is a fix possible / planned as of now? FF 96 will hit the release channel very soon on 1/11 which will affect a lot more users. |
I installed Firefox today on a new computer, and can confirm that I am having this issue |
I'm experiencing this after upgrading to FF 96.0 today. |
Just upgraded to 96.0 and also experiencing |
Same error here, i just updated to FF 96. Only happens in Firefox |
I haven't looked at this, but it's clearly important and manifesting for many users. PRs welcome!
…On Wed, Jan 12, 2022 at 3:57 PM, Omar Monrroy < ***@***.*** > wrote:
Same error here, i just updated to FF 96. Only happens in Firefox
—
Reply to this email directly, view it on GitHub (
#3964 (comment) ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAACDFQ4UAEHHTHHKQZYS43UVYIQLANCNFSM5JAUFTSQ
).
Triage notifications on the go with GitHub Mobile for iOS (
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
) or Android (
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
).
You are receiving this because you are subscribed to this thread. Message
ID: <philc/vimium/issues/3964/1011558962 @ github. com>
|
It seems Firefox 96 allows extensions to trigger native click behaviors. See philc#3964 for reports. Although this is not listed in https://www.mozilla.org/en-US/firefox/96.0/releasenotes/, I think it's safe enough to skip preventing since Firefox 96.
Happening on the general public releases now. 96.0.1 |
It seems Firefox 96 allows extensions to trigger native click behaviors. See philc#3964 for reports. Although this is not listed in https://www.mozilla.org/en-US/firefox/96.0/releasenotes/, I think it's safe enough to skip preventing since Firefox 96. (cherry picked from commit cf420fb)
It seems Firefox 96 allows extensions to trigger native click behaviors. See philc#3964 for reports. Although this is not listed in https://www.mozilla.org/en-US/firefox/96.0/releasenotes/, I think it's safe enough to skip preventing since Firefox 96.
Same issue here on 96.0.1 |
1 similar comment
Same issue here on 96.0.1 |
Same issue here on 96.0.1. I hope this gets fixed soon. |
Also seeing this issue. |
It seems Firefox 96 allows extensions to trigger native click behaviors. See #3964 for reports. Although this is not listed in https://www.mozilla.org/en-US/firefox/96.0/releasenotes/, I think it's safe enough to skip preventing since Firefox 96.
Thanks everyone for your patience. I've merged #3985 and will release to the extension stores later tonight. |
It looks like the Vimium extension has been updated, but I don't see anything for Vimium-FF...what is the difference between the two? It looks like they're both yours. |
@philc i think you pushed the update with a wrong extension name https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ is the original extension |
Ugh! Sorry folks. Yeesh. I’ll look at this tonight.
…On Fri, Jan 21, 2022 at 10:11 AM Artturi ***@***.***> wrote:
@philc <https://github.com/philc> i think you pushed the update to a
wrong extension name
https://addons.mozilla.org/en-US/firefox/addon/vimium/ was created
yesterday
https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ is the original
extension
—
Reply to this email directly, view it on GitHub
<#3964 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACDFXLVSW2LKVYCVLNXALUXGOVFANCNFSM5JAUFTSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I've updated vimium-ff ( https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ ) with the latest version — v1.67.1 — and put a notice on the vimium ( https://addons.mozilla.org/en-US/firefox/addon/vimium/ ) page to visit vimium-ff.
For historical context, at the time we published this extension for Firefox, "vimium" as a name wasn't available, but now it seems it is. I accidentally discovered this as part of the uploading process.
However, vimium-ff has the critical mass of users, so we'll keep using that.
…On Fri, Jan 21, 2022 at 2:27 PM, Phil Crosby < ***@***.*** > wrote:
Ugh! Sorry folks. Yeesh. I’ll look at this tonight.
On Fri, Jan 21, 2022 at 10:11 AM Artturi < notifications@ github. com (
***@***.*** ) > wrote:
>
>
>
>
>
>
> @ philc ( https://github.com/philc ) i think you pushed the update to a
> wrong extension name
> https:/ / addons. mozilla. org/ en-US/ firefox/ addon/ vimium/ (
> https://addons.mozilla.org/en-US/firefox/addon/vimium/ ) was created
> yesterday
>
>
>
> https:/ / addons. mozilla. org/ en-US/ firefox/ addon/ vimium-ff/ (
> https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ ) is the original
> extension
>
>
>
> —
> Reply to this email directly, view it on GitHub (
> #3964 (comment) ) , or
> unsubscribe (
> https://github.com/notifications/unsubscribe-auth/AAACDFXLVSW2LKVYCVLNXALUXGOVFANCNFSM5JAUFTSQ
> ).
> Triage notifications on the go with GitHub Mobile for iOS (
> https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
> ) or Android (
> https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
> ).
> You are receiving this because you were mentioned. Message ID: <philc/vimium/issues/3964/1018745478
> @ github. com>
>
>
|
@philc I still have this issue even after updating to v1.67.1 the same goes for https://addons.mozilla.org/en-US/firefox/addon/vimium/ |
The update to v1.67.1 fixes the double-open issue for me but seems to have swapped the functionality of I restarted Firefox to make sure this was not a transient problem but it persists. TBH I do not see anything in the code modification which could cause this but I am not really a web extension developer. AFAICT this seems to be caused by setting "When you open a link, image or media in a new tab, switch to it immediately" in the Firefox options, i.e. when this option is activated, the two Vimium functions are swapped. They only work as expected if the Firefox option is not active. OTOH I have this option set since ages and only experienced the incorrect Vimium behavior since the extension update. For the time being I can work around the problem by simply using the "wrong" Vimium command. Should I file a new issue for this? |
@xstnztk It's because old versions of Vimium "simulates" This is a new issue: do we need a new command option for |
Hi, As such I'm closing this bug as fixed. Cheers! |
Coincidentally, this perturbance might've fixed a long-standing annoyance that new tabs were always opened by Vimium right after the currently active one—instead of one after another rightwards (and FF didn't provide APIs to open them in a proper order). Unless some other change was made to that end. |
Agreed. This was always a minor annoyance for me as well. Now fixed. |
Excuse me, this issue it's fixed in FF Developer Edition but still happens in Firefox to me |
@drk01 Sorry but what's the versions of your 2 Firefox and their Vimium? |
@gdh1995 FF 96.0.2 & FF Developer 97.0b3. |
Same here, still happening to me on 1.67.1. However if I install the extension in a fresh profile, then it doesn't happen on that profile. Will try to figure out what setting / extension is causing it. |
It's |
Well, it's a same bug caused by fake |
Hi,
When I'm using shift + f to open a link in a new tab, instead of one tab two tabs with the same content appear.
I'm using Firefox Nightly and this started happening 1-2 days ago. Here's at least one more user experiencing the same problem #3579 (comment) .
Anybody else affected?
The text was updated successfully, but these errors were encountered: