Skip to content

Provide an option to use No Container as the default container #106

@Nepherte

Description

@Nepherte

Note: More a feature request than anything else.

Before v3.5 I've specified a bunch of rules for frequently visited sites to break out of an existing container and fall back to "No Container". What I truly intended is for any site that doesn't have a rule, to break out of a container.

Starting with v3.5 I can use the "Default Container" option to break out of any other container if the domain doesn't match any specified rule (which is great).

What would be even more awesome is if I could repurpose "No Container" as the "Default Container". Why? Whenever I want to branch out of whatever it is I'm doing in the current tab, to open up a new tab, which in turn loads the home page configured in Firefox (in my case a search engine). This home page is not matched by any rule, which would trigger the deletion of the tab and re-opening the page in the default container.

I'm probably nitpicking here (I acknowledge that other user's browsing patterns may differ), but this saves me a couple seconds each time I open up a new tab. For sure, there may be another add-on that allows me to open tabs in a specific container (the default one), but this sounds like a nice addition to Containerise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions