Closed
Bug 1226054
Opened 10 years ago
Closed 5 years ago
User is not automatically signed into their Pocket account after creating and verifying their Firefox account
Categories
(Firefox :: Pocket, defect)
Firefox
Pocket
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: wselman, Unassigned)
Details
This issue was revealed in the course of conducting user research with Pocket. Specifically, this issue occurred for participants who created a Firefox account in order to use Pocket.
After the user successfully completes the FF account form and then verifies their account, they return to the Pocket icon. Unfortunately, the user is not automatically logged into Pocket after FF account verification. Instead the user sees the original pane requesting the creation of a Firefox or Pocket account. More than one participant in the study was confused and believed that the Pocket sign up process did not work or complete correctly. After some confusion, the user has to locate the sign in link and sign in.
Expected behavior: The process should behave the same for users who create a Pocket account using email or by creating a Firefox account. After verifying a Firefox account, users should automatically be logged into their Firefox account and see their Pocket list when they click the Pocket icon, not the sign-up pane. Users who sign up using email to create a Pocket account are automatically logged in after account verification.
Comment 1•5 years 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: 5 years ago
Resolution: --- → INACTIVE
Comment 2•5 years ago
|
||
Jessilyn Davis what do you mean by "Discovery Stream-powered New Tab experience, and improvements to Pocket’s integration with Firefox."?
The issue still exists in FIrefox 73.0.1
Please reopen this issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•