Browser- File - New Container Tab

[Shoalsteed]

Trying to access the console or mail from this tab takes me to the Extension home page.
However , if I choose the I2P Browser, it does open a functional tab and I can get to an I2P site.

[eyedeekay]

I cant change this, container tabs can't set individual homepages. The closest I can get is to override them with the extension homepage. I might be able to figure out some kind of workaround but this one might need to be a wontfix

[Shoalsteed]

Just so I understand: none of these ( ( Dispatch, MuWire, Etc) have any linking functionality?

[eyedeekay]

They can be forced into the internal extension page but the user needs to click the respective link on the extension page to reach the application. I might be able to work around it by redirecting but I don't know if I can reliably tell that it's the first time they've opened the tab. Could end up with situations that spam a bunch of tabs because it keeps trying to re-isolate.

[Shoalsteed]

Since these redirect to the home page , then maybe just have a note in the applications section with email, hidden services, and snark that any applications that are available in your console will open in a container ?

[eyedeekay]

Ok sure. However, the rule for containerizing in this plugin is that if it's not happening automatically, then it's broken and the real problem is that. They shouldn't, and as far as I know, aren't, able to approach any console page, application, or I2P site from a path where the automatic isolation isn't triggered, in fact the entire UI is just different ways of triggering the automatic isolation function. This workaround is only necessary when triggering it from Mozilla's container-tab UI, and not from the browserAction menu or any of the myriad ways of automatically triggering the isolator, and it doesn't actually require them to read the warning to work correctly, and not because the normal isolator isn't working, just because there can only be one homepage.

[Shoalsteed]

Ok sure. However, the rule for containerizing in this plugin is that if it's not happening automatically, then it's broken and the real problem is that. They shouldn't, and as far as I know, aren't, able to approach any console page, application, or I2P site from a path where the automatic isolation isn't triggered, in fact the entire UI is just different ways of triggering the automatic isolation function. This workaround is only necessary when triggering it from Mozilla's container-tab UI, and not from the browserAction menu or any of the myriad ways of automatically triggering the isolator, and it doesn't actually require them to read the warning to work correctly, and not because the normal isolator isn't working, just because there can only be one homepage.

Yes, this sounds like the workaround.

[eyedeekay]

Current screenshot of the page they get redirected to if they open a tab from the File menu

[Shoalsteed]

Should this issue be closed?

[eyedeekay]

Yes I think so