-
-
Notifications
You must be signed in to change notification settings - Fork 252
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
Simple Tab Groups refuses Vimium C to open tabs in "No container" #198
Comments
I've reproduced this. This is a logic conflict between common extensions who want to create tabs, like Vimium C, and the Simple Tab Groups. According to code, Vimium C can not affect the SimpleTabGroups's process of forcing new tabs created in a special tab container. So you'll have to wait for the author to fix Drive4ik/simple-tab-groups#655. |
Hello, I got an idea to solve this conflict, and please try this version of Vimium C: vimium_c-1.84.3-firefox-a2a88e7.zip Installation: see https://github.com/gdh1995/vimium-c/wiki/Test-a-zip-package . With this version, you'll need to change mappings of
This is to ensure the newly tab belongs to a same container of a current tab's. |
um, oh I forgot this issue is about Vomnibar. I just fix broken createTab.
BTW, you ned to replace *** with your wanted keys.
…---Original---
From: "Zeioth"<notifications@github.com>
Date: Sat, Aug 22, 2020 02:53 AM
To: "gdh1995/vimium-c"<vimium-c@noreply.github.com>;
Cc: "Comment"<comment@noreply.github.com>;"Dahan Gong"<gdh1995@qq.com>;
Subject: Re: [gdh1995/vimium-c] Simple Tab Groups refuses Vimium C to open tabs in "No container" (#198)
Extension Last Updated
August 21, 2020
I clicked "save".
I opened a new page
I press B to load from bookmarks
I press ctrl+shift to load it in a new tab.
But I still get the message. Perhaps my mappings were not correct?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Please try this: vimium_c-1.84.3-firefox-9555c57.zip
The above only fixes URLs from Vomnibar would be blocked, and you'll need to re-map all commands which are related about "open a URL" and add a new option of
Note: the code above is only an example, so you'll need to use your preferred keys to replace those |
I can confirm, that config fixes the issue! I've tried the next with the parameters of your last post and it works fine:
Out of curiosity, I have a question: |
On Vomnibar, Ctrl+Enter opens a suggestion item in a new tab and focuses it, and Ctrl+Shift+Enter will only open but not focus. |
Feel free to close the issue now, or when you push the code. Thank you so much!! |
Hello, the v1.85.0 has been released on Firefox Add-ons, and you may take a try. |
Thank you for telling me! I've updated to the latest version, and tested i,t and it's working correctly as long as I write the settings you provided me. Maybe It would be a good idea to make them default? As long as there's no more issues involved. |
It will affect the relations among tabs. for example, if another builda a tab tree, then those tabs from vomnibar / createTab should be roots, but not children of a common web page.
…---Original---
From: "Zeioth"<notifications@github.com>
Date: Sun, Aug 23, 2020 20:14 PM
To: "gdh1995/vimium-c"<vimium-c@noreply.github.com>;
Cc: "Comment"<comment@noreply.github.com>;"Dahan Gong"<gdh1995@qq.com>;
Subject: Re: [gdh1995/vimium-c] Simple Tab Groups refuses Vimium C to open tabs in "No container" (#198)
Thank you for telling me! I've updated to the latest version, and tested i,t and it's working correctly as long as I write the settings you provided me. Maybe It would be a good idea to make them default? As long as there's no more issues involved.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I just noticed, NewTabAdapter is also affected by this issue: If I try to use any of the previously mentioned shortcuts from NewTabAdapter start page, I get the "Can't open url in the personal container" error. Also when I enter the starting page, if one is provided. |
sad. the extension is a bit annoying.
then i'll add an option to let adapter do the same logic like vimium c.
…---Original---
From: "Zeioth"<notifications@github.com>
Date: Sun, Aug 23, 2020 21:54 PM
To: "gdh1995/vimium-c"<vimium-c@noreply.github.com>;
Cc: "Comment"<comment@noreply.github.com>;"Dahan Gong"<gdh1995@qq.com>;
Subject: Re: [gdh1995/vimium-c] Simple Tab Groups refuses Vimium C to open tabs in "No container" (#198)
I just noticed, NewTabAdapter is also affected by this issue:
If I try to use any of the previously mentioned shortcuts from NewTabAdapter start page, I get the "Can't open url in the personal container" error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Please test this: Show advanced options, enable the "Open target URL in a same container (group)." and then test it with Simple Tab Groups enabled. |
Please try this: newtab-1.2.0.zip. Currently there's a limit: if |
I just tested it, I can confirm it works. I can't tell you how happy I am to have that annoying message out of my life. Thank you!!! I'll close the issue as soon as the new version is live. |
NewTab Adapter v1.3.0 has been released. |
For those coming here later, the solution to this is to add |
Problem:
There's no way to dismiss the alert forever.
How to reproduce:
Everytime you do it, you'll see the next window.
![Captura de pantalla_2020-07-18_17-01-50](https://user-images.githubusercontent.com/3357792/87855536-51164200-c919-11ea-82c7-8fc8fe302608.png)
What should happen: Give the user an option to remember the selection, and don't show the page again.
Related links:
The text was updated successfully, but these errors were encountered: