I am going through somewhat lengthy explanations and using interactive graphs in 2D and 3D. My goal is to introduce things gradually and provide different perspectives to increase the chance of at least one clicking.
It’s in no way complete. In fact, it currently only has one chapter. But I am actively working on it. Hope you like it.
With current discussions on HN about Firefox containers, I figured it’s a good time to share my recently released extension for Firefox containers called “Container Default Pages”.
As the name suggests, it lets you assign a default page for each container. Similar to how you have a homepage for your browser, you now have one for each container.
The primary use case is the following. When you have a container dedicated to say, YouTube, it makes sense that when you open a new tab in your ‘YouTube Container’ it should go directly to YouTube. Of course you can open other things but the extension provides a convenient default behavior.
A plus is that the extension doesn’t ask for permissions and it’s lightweight. You just do the easy setup of assigning default pages to your containers, then it becomes a natural part of your workflow. Please try and let me know what you think.
Some background info about Firefox containers for those unfamiliar:
Firefox containers allow you to create different environments in your browser. The basic functionality is built in Firefox. There are extensions that makes using them more convenient. For example, the Facebook Container extension [0] isolates Facebook and its subdomains and forces it to open in that container. There’s also the Multi-Account-Containers [1] which gives you more power by managing multiple containers. Unlike Facebook Container, it’s not preset up. You need to create the containers for the websites you need. But it’s nice in that it gives features that can work for all websites, such as directing websites to certain containers.
More info about containers [2].
Speaking of Firefox containers, I created an extension that adds an extra layer of convenience. The extension lets you create a default page for each container; something like a homepage for each container. It’s called‘Container Default Pages’ [0]
One thing the Multi-Account-Container does is allow you to redirect a website to open in a specific container. My extension gives the extra feature of assigning the container itself to a default website.
The main use case is when you have a container dedicated to say, YouTube, it makes sense that when you open a new tab in your ‘YouTube Container’ it should go directly to YouTube. Of course you can open other things but the extension provides a convenient default behavior.
Then I think you'll also love the Container Default Pages extension [0]. I lets you assign a default website for each container. So for example if you have a container just for YouTube, you can set YouTube to open automatically when you open a new tab in that container. It's very convenient.
Disclosure: I created it.
The extension already supports that, albeit in a semi-convoluted way: you have to visit the site to set a default container for it. If yours let's you edit it by hand, that is a pretty big quality of life improvement.
I think what you're referring to is the "Always Open This Site in .." option. That one assigns a website to automatically open in container. This on the other hand, assign a container to a default page. It's similar to how you have home page for your whole browser, but now for each container.
I am going through somewhat lengthy explanations and using interactive graphs in 2D and 3D. My goal is to introduce things gradually and provide different perspectives to increase the chance of at least one clicking.
It’s in no way complete. In fact, it currently only has one chapter. But I am actively working on it. Hope you like it.