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

3.1.0 update breaks compatibility with Temporary Containers #70

Closed
lucassz opened this issue Jul 8, 2019 · 8 comments
Closed

3.1.0 update breaks compatibility with Temporary Containers #70

lucassz opened this issue Jul 8, 2019 · 8 comments

Comments

@lucassz
Copy link

lucassz commented Jul 8, 2019

Containerise was coexisting wonderfully with Temporary Containers for me until the 3.1.0 update, but the change to have "all unmapped urls now open outside of any container" seems to have broken the compatibility with TC's Isolation Mode.

@Radagast
Copy link

Radagast commented Jul 9, 2019

I'm not sure the only issue is with temporary Containers. For me, with Containerise alone I get two tabs opening for any link to a site with a defined container. With TC enabled it can be multiple tabs. Unfortunately, TC also got an update today too. That said, reverting to 3.0.1 seems to fix the issue.

@pezz
Copy link

pezz commented Jul 9, 2019

Is there somewhere I can download the 3.0.1 xpi from until this is fixed?

Cheers.

Edit: never mind, addons.mozilla.org has it.

@dboy591
Copy link

dboy591 commented Jul 9, 2019

The breakage with TC seems to be due to the lack of a "No Container" in this latest version of Containerise. Manually reverting to the previous version for now.

@kintesh
Copy link
Owner

kintesh commented Jul 9, 2019

I will revert the last change. Ideally you should only be using one container add-on as you always run into race condition. FYI I personally stopped using any container extension. So when I develop I don't test comparability with other similar extensions.

@arlavit
Copy link

arlavit commented Jul 9, 2019

I will revert the last change. Ideally you should only be using one container add-on as you always run into race condition.
No way. Every extension has its own features, so one will lose on this.

@vshl
Copy link

vshl commented Jul 9, 2019

"all unmapped urls now open outside of any container" should be optional. For instance, if I have two twitter accounts: one personal and one work, I cannot manually assign these twitter accounts to 2 different containers like my current usage.

@tomose
Copy link

tomose commented Jul 9, 2019

I will revert the last change. Ideally you should only be using one container add-on as you always run into race condition. FYI I personally stopped using any container extension. So when I develop I don't test comparability with other similar extensions.

I'm on Waterfox with no other container addons and experience the issue of blank tabs opening as well. So it may not be an issue totally exclusive to having multiple container addons.

@kintesh
Copy link
Owner

kintesh commented Jul 9, 2019

All the changes of v3.1.0 are reverted in v3.2.0

@kintesh kintesh closed this as completed Jul 9, 2019
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

Successfully merging a pull request may close this issue.

8 participants