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

Add hook for ignoring "always open in" setting #1414

Closed
lonix1 opened this issue May 11, 2019 · 4 comments
Closed

Add hook for ignoring "always open in" setting #1414

lonix1 opened this issue May 11, 2019 · 4 comments
Labels
Component: Site Assignment Issues related to assigning a site to a container 👍 Feature Request Feature requests users would like to see in this addon

Comments

@lonix1
Copy link

lonix1 commented May 11, 2019

If "always open in container" is selected, then that behavior is impossible to circumvent.

Other addons (e.g. Context Plus) which allow to reopen or move a tab to a different identity (/tab) won't work because the move is intercepted by this addon, and the "always open in" policy is enforced.

It would be nice if there were some sort of hook that allowed this addon to work well with other addons, so that this feature would be ignored if allowed by the user.

@vinzent
Copy link

vinzent commented May 15, 2019

I think this relates to my issue/request: #1410

@lonix1
Copy link
Author

lonix1 commented May 15, 2019

Related but not the same thing. Your issue is part of firefox itself, whereas this is about interoperability with other addons.

We need the ability to 1) move container tabs around, and 2) move them between "identities" as made possible by other addons.

@grahamperrin
Copy link

Is this a duplicate of #1222?

@dannycolin dannycolin added 👍 Feature Request Feature requests users would like to see in this addon and removed enhancement labels May 20, 2022
@dannycolin dannycolin changed the title [Feature Request] Add hook for ignoring "always open in" setting Add hook for ignoring "always open in" setting Jan 6, 2023
@dannycolin dannycolin added the Component: Site Assignment Issues related to assigning a site to a container label Jan 6, 2023
@dannycolin
Copy link
Collaborator

  1. move them between "identities" as made possible by other addons.

The main concept is to isolate each container from the others. This would go against that principle. So if by moving identities, you also mean moving the data for this site (cookies, local storage) this won't happen.

I do thing allowing a way to open only an assigned website with "re-open" is a valid use case without copying the data to the second container.

With that in mind, I'll go ahead and close this as a duplicate of #1442 that should solve this part of the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Site Assignment Issues related to assigning a site to a container 👍 Feature Request Feature requests users would like to see in this addon
Projects
None yet
Development

No branches or pull requests

5 participants