Discord site tries to exit the container, causing a loop of creating tabs

kintesh / containerise

Firefox extension to automatically open websites in a container

MIT License

408 stars 54 forks source link

Discord site tries to exit the container, causing a loop of creating tabs #168

Closed ghost closed 2 years ago

ghost commented 2 years ago

I have these rules in place:

.discord.com , Discord .discordapp.com , Discord *.discordapp.net , Discord

They've all worked in the past. Recently, if I clicked a link pointing to discord's servers, it would enter an endless loop of opening a new tab, closing the current one, repeat.... I disabled containerise, opened a new tab in the Discord container, typed in the URL (discordapp.com) manually, and it opened a new tab outside of the container. I guess with containerise in place, discord is not allowed to open in the default container, and it won't allow to open outside of it, so it loops.

I don't think this is a containerise bug, it may be a firefox bug I'm unsure (I don't think discord should be allowed to break out of its container?), but basically, it's discord being shady as usual, and the result is an unresponsive browser.

crssi commented 2 years ago

For sure you need to add discord.com , Discord for discord.com to be opened in Discord container.

ghost commented 2 years ago

For sure you need to add discord.com , Discord for discord.com to be opened in Discord container.

The rule is in place and working, discord tabs are opened in the discord container, but the website then opens itself in a new tab in no container.

...Which is forced by containerise, to open in a Discord container tab ...but the website then opens itself in a new tab in no container. ...Which is forced by containerise, to open in a Discord container tab ...but the website then opens itself in a new tab in no container. ...Which is forced by containerise, to open in a Discord container tab ...but the website then opens itself in a new tab in no container.

....This goes on forever.

ghost commented 2 years ago

I've managed to track this down. Somehow, this setting in MAC was enabled.

The list is empty so containerise was forcing the site into a container and then MAC was forcing it out of the container.

It wasn't me, I didn't even know this setting existed until I traced it just now. I'll close this case but hopefully it might help if this behaviour crops up again, which I get a funny feeling it will.....