-
Notifications
You must be signed in to change notification settings - Fork 1
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
Two tabs open for "Always Open This Site in..." #11
Comments
Adding to this that there are still a couple of scenarios that this results in duplicate tabs that can't be avoided:
Hence, it would be nice if this add-on could check if the site isn't already being opened in a container prior to assigning it a new container. |
Should be closed by #13 . |
This looks promising, thanks @dvngn for working on this. Unfortunately, I just updated to v1.3.0 and the behaviour hasn't changed for me. Two tabs open whenever I open an URL that has been set to "Always open in". |
Could you list all of the extensions used in your browser? Thanks. |
I have just tested this after turning off all my extensions except I'm using:
Other extensions I normally have active (but I doubt this is relevant, because the issue persists with these turned off):
|
I have 1.3.0, but still seem to have this issue in combination with "always open in" option from multi account containers.... |
This issue is also still appearing for me on v1.3.0. Sometimes when I open a shortcut it works, but sometimes two tabs still open. |
Great add-on for Firefox, especially after the sad news about Temporary Containers.
The only issue that I'm having it that when I open a website, that has a default container set, in a new tab (middle-mouse click or ALT+ENTER), two tabs are opened. Both these new tabs are for the same container.
The work-around is to simply not use the middle mouse button or ALT+ENTER, but then the new tab doesn't appear at the end of all the open tabs but next to the current tab. Not a big inconvenience, but figured I would comment here for others to find the workaround (and hope for a fix).
Now off to retrain my muscle memory ;)
The text was updated successfully, but these errors were encountered: