Multi-account containers cannot be set as default for new site
Categories
(WebExtensions :: Developer Outreach, defect, P5)
Tracking
(firefox66 unaffected, firefox67 affected, firefox68 unaffected)
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | unaffected |
| firefox67 | --- | affected |
| firefox68 | --- | unaffected |
People
(Reporter: gerbert.jansen, Unassigned)
Details
(Whiteboard: triaged)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
- Open new site in 'shopping'container
- using the multi-account containers toolbar button, check 'Always open in Shopping'
- close tab
- reopen the site in a regular tab
- Firefox asks 'Open this site in your assigned container?'
- check 'remember my decision for this site', and click 'open in shopping container'
- nothing happens, got stuck on this page
Actual results:
- Open new site in 'shopping'container
- using the multi-account containers toolbar button, check 'Always open in Shopping'
- close tab
- reopen the site in a regular tab
- Firefox asks 'Open this site in your assigned container?'
- check 'remember my decision for this site', and click 'open in shopping container'
- nothing happens, got stuck on this page
Expected results:
- Open new site in 'shopping'container
- using the multi-account containers toolbar button, check 'Always open in Shopping'
- close tab
- reopen the site in a regular tab
- Firefox asks 'Open this site in your assigned container?'
- check 'remember my decision for this site', and click 'open in shopping container'
- site opens in the requested container
Comment 1•6 years ago
|
||
Hi GAj,
I tried to reproduce the issue on the latest Beta 67.0b8 and did it only once. Installed the multi-account container addon and followed the steps provided.
Clicking for the first time on the "open in shopping container" button didn't work, waited 2 seconds and it did work afterward..Could not reproduce after this no matter how many new profiles I created.
Gaj, can you reproduce this every time with a new profile and only multi-account container addon installed?
Hi Timea,
As you requested, I have tried to open a tab in a just assigned shopping container (as described previously above) in 2 new profiles on Beta 67.0b8 with only multi-account container installed.
Unlike you, I am not able to get past the 'open in shopping container' (remember my decision is checked), no matter how many times I click the button, or how long I wait (> 5 min).
N.B. FYI: I remember that in previous (early 60's version) beta-builds the same problem occurred, but I never reported this. And as far as I know, I never had the issue in any stable release.
Comment 3•6 years ago
|
||
Reproduced on Ubuntu 16.04 and Windows 10 x64 once more. Strangely it either works for me after waiting 5 seconds or I close and re-open the same page that I used to open in a container.
Reproduced only on latest Beta. Couldn't reproduce on Release 66 nor on Nightly 68.
Attached is a screenshot of the browser console log (unnaffected Nightly and affected Beta): https://imgur.com/dBNmR92
Also tried to reproduce on Nightly, only difference I can see in browser console logs is that on Nightly there is one warning log that does not appear on Beta:
- "LoginRecipes: getRecipes: falling back to a synchronous message for: moz-extension://62430d94-3bf6-4ca9-9c85-82b404008e7a"
Moving this over to the component.
Thanks for the report GAJ!
Updated•6 years ago
|
Updated•6 years ago
|
Comment 4•6 years ago
|
||
Hi Jonathan, could you (or a member of the Multi Account Containers team) look into this?
Comment 5•6 years ago
|
||
This looks like a duplicate of https://github.com/mozilla/multi-account-containers/pull/1387 so I'm going to close this. I haven't been able to reproduce this bug in any other way than that issue there.
This bug should be merged tomorrow and go live shortly.
Comment 6•5 years ago
|
||
This bug has been occuring reliably for a long time (years) for me. It's a tough one because it's so erratic with no apparent logic - probably in three of four cases, it will finally register the click after 10-20 clicks.
Not so today - the button just won't work at all today. Maybe because of how Sirius is aligned to Proxima Centauri right now.
I will try to narrow it down and see if I can find a pattern when I have more time. I'll post any findings back here.
Updated•3 years ago
|
Comment 7•2 years ago
|
||
Closing as incomplete, based on the previous comments it seems that part of this issue was meant to be fixed by the changes linked in comment 5, but based on comment 6 it seems this may have still be happening but it was still not clear which STR would trigger it consistently and help the extension developers to investigate the issue further.
Description
•