-
Notifications
You must be signed in to change notification settings - Fork 350
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
Refreshing a website assigned to a different container wrongly opens the "Containers confirm navigation" page in a new tab #635
Comments
I would say that the opening in a new tab is expected, unless a way to switch a tab from container has been implemented. However, the issue I see here is that the new tab is not in the right container. |
This seems a lot like: #626 I guess we didn't fix it there? |
Sorry I understand this now, it is kinda expected. Currently we allow "Exemptions" to assignment, issues I see with this related to this and other bugs that might come up:
The issue here is 2. and I think we can fix this when the user assigns the tab.
|
… set based on existing tabs. Fixes mozilla#635
The issue is no longer reproducible on the latest Containers add-on built on 6/28/2017. |
[Affected versions]:
[Affected Platforms]:
[Prerequisites]:
[Steps to reproduce]:
[Expected results]:
[Actual results]:
[Notes]:
The text was updated successfully, but these errors were encountered: