STR: 1. Sign in to Firefox Account. 2. Wait a couple minute after sync gets finish. 3. In hamburger menu, click to FxA icon to open sync preference 4. In sync preference, click 'Manage account' link. Expected: It should open FxA setting page Actual: It asks user to sign in to FxA to continue. Please see video here: https://ranisharma22.tinytake.com/sf/MTU3NTAwN181NDAyNDI4 I could reproduce this issue 3-4 times in a row.
Thanks Kumar - in bug 1353571 you mentioned this might be a regression from that bug, but I doubt it is. We know there are a few issues related to this, but IIRC, they tend to be around either private-browsing, or when Firefox is set to never remember history - but in those cases I believe it is always reproducible. Shane, does this ring a bell to you?
This is to confirm that in this case it was neither private-browsing nor 'Never remember history'. Today again I encountered this issue multiple times on FxA custom test environment while testing 'Secondary email' feature.
This will likely be fixed by the Firefox patch Shane is working on in Bug 1308038. It sounds like this may be related to the way localStorage is handled in multi-process Firefox; if you disable multi-process Firefox does the problem stop occurring?
I couldn't reproduce this issue on the latest nightly today with multi-process on. I hit this bug again on custom testing environment where multi-process is disable. STR: 1. confirm sign-in through email 2. In hamburger menu, click to FxA icon to open sync preference - here it shows user is signed in. 3. In sync preference, click 'Manage account' link. Observation: It asks user to sign in to FxA to continue, and this time hamburger menu too shows user as not signed-in/disconnected sync. Earlier as shown in video of bug report, sync wasn't getting disconnected.
:markh - PB mode was always a problem, E10s was intermittent. I was able to reproduce 100% of the time in Nightly the other day after Ryan Feeley showed it happening on his machine. I wonder if this is a manifestation of . I haven't been able to find the bug where DOM storage in FxA embedded in about:accounts seems to be totally isolated from FxA's DOM storage in a normal tab.  - https://bugzilla.mozilla.org/show_bug.cgi?id=666724
(In reply to Shane Tomlinson [:stomlinson] from comment #5) > I haven't been able to find the bug where DOM storage in FxA embedded in > about:accounts seems to be totally isolated from FxA's DOM storage in a > normal tab. I bet that's because about:accounts is in the parent process (and maybe fallout from that new DOMStorage impl). Paul and I were just chatting about this same general issue WRT the benefits/tradeoffs of having accounts.firefox.com used in *both* the (ideally sandboxed) child and parent processes, and this bug seems related.
I'm closing this as a dup of #1308038 which has a patch in progress. Thanks Kanchan and the feedback :asuth!