Temporary-containers: New tab no longer opens Temporary Container with Automatic mode

[MzHub]

• Temporary Containers Version: 0.90
• Firefox Version: 60.0.1
• Operating System + Version: Windows 7
• Non-default Options/Preferences in Temporary Containers: Automatic mode on, middle and ctrl clicks always open new container.
• Other installed Add-ons + Version:
  Multi-Account Containers 6.0.0
  uBlock Origin 1.16.6

Actual behavior

New tab does not open in (or get replaced with) a Temporary Container.

Expected behavior

New tab opens in (or gets replaced with) a Temporary Container.

Notes

Just updated Firefox, didn't have this issue before.

[nameless3]

I can reproduce using the same version of Firefox and TC, however when I visit a website the tab does turn into a temporary container (except for about: pages after quick testing)

Seems like setting browser.newtabpage.enabled to true fixes it?

[Perflyst]

Seems to be a similar/same problem as #150

[stoically]

This should be fixed since Firefox version 61. Let me know if it's still a problem.

[Perflyst]

The issue is still persistent if about:blank is defined as default start page in about:config

[stoically]

@Perflyst I've changed the homepage to about:blank and with just Automatic Mode turned on in TC (everything else is default) pressing Ctrl+T (re)opens a new Temporary Container. This doesn't work for you?

[Perflyst]

Seems to be profile releated, just tested in a new one. Indeed is fixed since 61.

[ghost]

The issue is still persistent if about:blank is defined as default start page in about:config

Seems to be profile releated, just tested in a new one. Indeed is fixed since 61.

It still happens if you use blank pages. I was able to reproduce this in Firefox 65.0

1. Create new profile
2. Installed Temporary Containers
3. Set Automatic Mode
4. Installed a search instance. In this case I chose searx disroot
5. It worked until I changed the "Homepage and new windows" and "New tabs" to "Blank Page", changing it back to "Firefox Home" seemed to fix it.

As a temporary work around I just used "Firefox Home (Default)" and turned off Web Search, Top Sites, Highlights and Snippets for basically the same thing. I would like to know if it is possible with about:blank however and if there is some limitation what it is.

[stoically]

The issue is still persistent if about:blank is defined as default start page in about:config

5. It worked until I changed the "Homepage and new windows" and "New tabs" to "Blank Page", changing it back to "Firefox Home" seemed to fix it.

Was able to reproduce this for about:blank tabs. The problem is that TC only checks for about:home and about:newtab. However, just adding about:blank to the check doesn't work since the about:blank tab has its URL set onCreated but fires an onUpdated with about:blank as URL a bit later, resulting in two new tabs - have to figure out a way to circumvent that.

However, POST search engines wont work with the advanced automatic mode setting "Don't reopen" due to the way TC operates in that case.

[Gitoffthelawn]

@stoically Just FYI, you mentioned that TC checks for about:home and about:newtab. When I type about:newtab into the urlbar, it isn't opening in a container, even with automatic mode enabled.

[stoically]

Fixed in version 0.92. Let me know if something still doesn't work as expected.

[stoically]

FYI, upcoming version 1.4 will no longer reopen "Blank page" (about:blank) tabs due to all sorts of problems with the mechanism to detect that correctly. Would need an explicit API (or tab status) from Firefox. Reopening happens on first navigation instead in that case.