Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Have "Always open this site in..." distinguish between different paths in domains (foo.com/pathA vs foo.com/pathB) #2096

Closed
hub2git opened this issue Aug 6, 2021 · 5 comments

Comments

@hub2git
Copy link

hub2git commented Aug 6, 2021

I appreciate how useful multi-account-containers is. It's one of several reasons I love Firefox.

I suggest enhancing the "Always open this site in [specific container]" feature.

Currently, this feature can distinguish between domains, but it cannot automatically use different containers for different paths of the same domain.

When I go to reddit.com/r/someSubredditA, I want this extension to automatically use my "SeriousFace" container
When I go to reddit.com/r/someSubredditB, I want the extension to automatically use my "HappyFace" container.

Currently, it can't do that, and would open all reddit.com sites in the same container.

If I got my wish, "Always open site in..." would be renamed to "Always open path in..."

@okeegan
Copy link

okeegan commented Mar 22, 2022

Seconded, this drives me crazy with my multiple google accounts!

@achernyakevich-sc
Copy link

It looks it is another one duplicate. I would propose to try the way described in the comment.

@hub2git Could you close this issue to point other who will search for similar but more structured issue. :)

@hub2git
Copy link
Author

hub2git commented Mar 22, 2022

@achernyakevich-sc Hi Alexander, thanks for your comment on my issue-thread. Are you sure it's a good idea to close my issue?
My issue is number 2096, yet the thread you linked to is newer (2100).

@achernyakevich-sc
Copy link

@hub2git This is not about a number but about number of comments and exposed solution. :) For sure you could keep your issue open but I think everybody will just ignore it as there are dozens of this kind issue in this repository and people just ignore because of this fact. I could suspect you even created your issue have not read older closed threads for the same topic. So having one issue will really to help to concentrate on the real solution and comments why MAC developers will never implement it.

You could close is and leave the last comment that discussion moved to the #2100 thread so anybody who will come to your issue will switch there and continue there.

@dannycolin
Copy link
Collaborator

Duplicate of #691

@dannycolin dannycolin marked this as a duplicate of #691 Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants