Open
Bug 1261378
Opened 5 years ago
Updated 7 months ago
"View Pocket List" requires sign-in when opened in Private Browsing, although pocket saving works fine
Categories
(Firefox :: Pocket, defect, P2)
Tracking
()
People
(Reporter: pauly, Unassigned, NeedInfo)
Details
Attachments
(1 file)
|
318.01 KB,
image/png
|
Details |
[Affected versions]: - 46b6 [Affected platforms]: - all [Steps to reproduce]: 1. Start FX with a new profile 2. Sign in to Pocket 3. Open a new private window 4. Open a page and save it to Pocket 5. Click on the "View Pocket List" button [Expected result]: - "View Pocket List" shouldn't ask for credentials [Actual result]: - "View Pocket List" requires sign-in when opened in Private Browsing, although pocket saving works fine [Regression range]: - reproduced on FX 45, 48.0a1 (2016-03-31)
Comment 1•5 years ago
|
||
Again, if this applies to 45, why is this blocking bug 1215694 ?
Flags: needinfo?(paul.silaghi)
Comment 2•5 years ago
|
||
I'm not certain this is actually a bug. If anything, it is a bug that the pocket addon credentials are used in the private window.
No longer blocks: 1215694
| Reporter | ||
Comment 3•5 years ago
|
||
Pocked moved to a system add-on in bug 1215694, which landed on FX 46. So, I though all the new bugs should block bug 1215694. The 45 flag is set so people to know this is not a recent regression caused by the Pocket moving.
Flags: needinfo?(paul.silaghi)
Comment 4•1 year ago
|
||
This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience, and improvements to Pocket’s integration with Firefox.
Please help us triage by reopening if this issue still persists and should be addressed.
Thanks!
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INACTIVE
Comment 5•1 year ago
|
||
The behaviour in comment #0 still occurs; as comment #2 suggests, it's not clear which of the two cases (saving to pocket or showing the list) needs fixing here - but we should make a decision, the status quo is unexpected.
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Comment 7•1 year ago
|
||
NI'ing Product & UX for advice on how this should work.
Flags: needinfo?(tmiller)
Flags: needinfo?(tkanhema)
You need to log in
before you can comment on or make changes to this bug.
Description
•