Spawns tabs endlessly together with Containerise v3.1.0

[pezz]

• Temporary Containers Version: 1.0
• Firefox Version: 67.0.4
• Operating System + Version: Arch Linux
• Non-default Options/Preferences in Temporary Containers: Lots?
• Other installed Add-ons + Version: Multi-Account Containers, Containerise, Cookie Auto Delete

Noticed some strange behaviour by Firefox and saw that this addon updated.

This simply doesn't work as it used to. Any time a temp container is created a new tab is opened with the URL it and not in the temp container.

With automatic mode on this is especially bad as new tabs keep getting opened indefinitely.

Turning off automatic mode fixes the unlimited new tabs opening, but even without it nothing seems to open in a new temp container now.

[Radagast]

@pezz
Are you using Containerise?

I'm not completely sure where the problem is yet but the latter also had an update today and for me, reverting back to 3.0.1 fixed the issues with multiple tabs opening. TC is working correctly with Automatic mode on.

[pezz]

Ah, you are correct - Containerise was also updated, disabling it stops this from happening.

Might see about logging a bug there, cheers.

[crssi]

Quote from @dboy591

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/containerise#70 (comment)

[stoically]

Opened kintesh/containerise#74 over at Containerise to hopefully get a fix in soon. The only thing I could do in TC is completely disable TC if that Containerise version is detected.

Reopening for visibility.

[TiagoTiago]

It's not the first time this addon has been involved in an infinite tab-opening bug; maybe it might be a good idea to add a check for having opened new tabs with the same URL too many times in a row in the last few seconds, and then just replace the URL with one pointing to an error message suggesting an workaround with a link to try to open the URL anyway?

[stoically]

Yeah, I agree that having a fail-safe would be good for incompatibilities of this kind. Maybe I get around to implement one this time (and don't forget it again).

[stoically]

FYI, Containerise is planning to revert the change causing this issue: kintesh/containerise#70 (comment)

[stoically]

Fixed (reverted) in Containerise v3.2.0