-
Notifications
You must be signed in to change notification settings - Fork 348
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
stop asking me #2256
Comments
@exekutive , it looks like you have activate the You could try to do it by one of the way described in the following comment. Please, close your issue if the advise will help. :) |
instructions are unclear
right-click where?
This worked , but I had to search through all the containers to find the site. Thank you. |
Strange that it is complicated. :) See more details and screenshot below.
Anywhere on the page that was open in undesired container. As result you will see context menu like this: And you will need just untick
You needed just to check the page and name of the container it was open in. Like in red circle on the screenshot below: and check manage that container settings to exclude site from it. @exekutive, it looks like your problem is resolved so could you close this GitHub issue to show other people that correct answers available in comments. :) |
ok I found it. Again , thank you and keep up the good work. |
I've just discovered how I've been accidentally ending up with sites assigned to a container – this icon in the address bar, which I've never paid much attention to, and occasionally use without thinking. It looks very similar to the "Multi-Account Containers" icon outside the address bar (on the right of the toolbar in this screenshot). But when you click it, it assigns the current site to a container. Unfortunately there is no preference in the extension to remove it. |
whenever I try to browser to a site A, by simply typing it in the address bar, I get a page saying
I don't remember ever asking Firefox to do that. How do I un-ask it?
The text was updated successfully, but these errors were encountered: