Closed OUguy314 closed 6 years ago
Which website are you trying to assign?
In this case, I was trying to assign http://www.facebook.com, but this bug happens with all other websites, too.
I can confirm this bug. Same thing happens to me.
One more confirmation (win 10, FX beta 64 bit, test-pilot add-on). Same behaviour as described by babant:
I resolved issue by deleting container in question, and uninstall-install of the container add-on (just deleting affected container didn't help)
Works for me since version 57.0b1
And still works on 57.0b3
So even though this likely now works for existing containers I think some users still have stale assignments. There is also a chance that you have a disabled extension whilst the container is deleted or perhaps some other code issue doesn't handle the container event (which will likely still happen for stable users.)
My latest commit actually checks before showing this assignment and continues to the page if the container no longer exists. I think the resilience of containers is worth the perf hit here.
When I try to set a website to always open in a container, after hitting "open in container" to set a site to always open in a container, it then asks "You asked Firefox to always open for this site: null" in an endless loop.![untitled](https://user-images.githubusercontent.com/31787440/30240270-84fd9078-9532-11e7-8398-12e1eb10347f.jpg)
Steps to Reproduce: