Skip to content
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

"Reopen in container > No container" isn't respected #2

Open
kemayo opened this issue Jun 27, 2018 · 4 comments
Open

"Reopen in container > No container" isn't respected #2

kemayo opened this issue Jun 27, 2018 · 4 comments

Comments

@kemayo
Copy link
Owner

kemayo commented Jun 27, 2018

The multi-account-containers add-on adds a right-click menu on a tab, to let you open it again in a different container. "Reopen in no container" is being treated the same as opening a new tab, and getting the current container applied.

So: work out how to tell when this happens, and ignore it.

@m4dc4p
Copy link

m4dc4p commented Oct 2, 2018

Would love to see this behavior addressed. However, I love this extension so much regardless. Great work!!!

@omgitsraven
Copy link

Is there any known workaround for this until it's fixed? I was enjoying this extension until I realised I'd closed my last open no-container tab, which meant I had to disable the extension entirely in order to make a new one so I could access my no-container logins

@m4dc4p
Copy link

m4dc4p commented Apr 10, 2019

@omgitsraven I no longer use this extension as "Conex" (https://github.com/kesselborn/conex & https://addons.mozilla.org/en-US/firefox/addon/conex/) includes the same functionality and works really well.

@joncamfield
Copy link

Flagging that in addition to this "unexpected" result, it also prevents LastPass (and likely other similar plugins) from being able to work well across different containers. This shows up when LP tries to open a new system tab to edit/add/open the vault/change settings, and it gets "captured" in a sticky container where LP has not been activated.

I imagine there are also some people who may set up password managers to be constrained within containers, so resolving a no-container approach that can work across containers should be addressed in a way that doesn't interfere with stricter per-container plugin management (if that's possible and remotely common?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants