cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
justanotheruser
New member
Status: New idea

I've really come to appreciate the container feature, but they're still completely manual.

I'd suggest to add a feature to bookmarks and bookmark handling, so that I can specify in a bookmark, in which container it will open.
The idea is to have e.g. one bookmark "Google/Docs/YT (work) to open in my "work" container with my work login, and another one to open in a standard container with a different or no login. Currently, this works just fine, but I have to open the container tab manually each time.

(This could be a more flexible addition to pre-assigning e.g. all *facebook.com domains to one container as @bugboy  suggested.)

30 Comments
Rowolfs
New member

Open containers from bookmarks

Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

Feel free to use this space to add more details to your idea and respond to any incoming comments from other community members 😃

Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

3133Alex
Making moves

It would be nice to have bookmarks open in specific containers. E.g. I have some work-related bookmarks that I always want to open in my work container. This feature would allow bookmarks to be associated with a container, so that when the bookmark is opened with a left-click, it opens in that container by default.

Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

forrie
Making moves

Would it be useful if the bookmarks themselves could be configured to simply open in a specified container?  As I understand now, I need to manually do this, which can be cumbersome.

Also, if I open a new tab from another container, it would be useful (to me) if that new tab opened in that container.  

Some minor adjustments to this functionality might make this go more smoothly?

Thanks!

forrie
Making moves

It seems to me that this design really needs a "Default Container"

Logic suggests that if a user is utilizing containers, then opening a site in a non-container manually should be the option, rather than default.

 

forrie
Making moves

(I can't edit my prior post)

COMMAND+T opens a new tab, but there is no ability to define keys to open containers.

COMMAND+T should optionally open a user-specified Default Container.   There could be other keystroke definitions (user specified?) to open specific containers.   In Bookmarks, that link should optionally have a definition to open in a specific Container.

I think these make sense from a UX perspective.

forrie
Making moves

Should some Containers remain behind, and be allowed to store cookies within?

Let's take Facebook as an example.  If you've enabled 2-factor authentication, once your container is closed, you have to re-login and go through all of that.   If the Container is prevented from accessing anything else, a user-configurable option to keep cookies in a container might make some sense -- this applies to other services that require you to log in.  Again, Optional.

Mozilla might implement something like this for the URL bar:

container://[container name]/[full URL, including http?]

or

container[0-10]://website

Whichever has the broadest useful impact.

forrie
Making moves

A potential bug or feature issue.   I can choose that a site like Google always opens in a certain container.  BUT, if I go to a sub-service like translate.google.com, it doesn't open in a Google container. 

Should we have the ability to wildcard a domain into a container?