Pocket pop-up isn’t displayed and the user is redirected to the getpocket.com

RESOLVED INVALID

Status

()

Firefox
Pocket
RESOLVED INVALID
a year ago
a year ago

People

(Reporter: CosminB, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox52 unaffected, firefox53 unaffected, firefox54 unaffected, firefox55 unaffected)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8854402 [details]
Pocket.gif

[Affected versions]:
- Firefox 52.0b9 (20170223185858)
- Firefox 52.0.2 (20170323105023)
- Firefox 53.0b9 (20170403072723)
- Firefox 54.0a2 (2017-04-04)
- Firefox 55.0a1 (2017-04-04)

[Affected platforms]:
- Windows 7 64-bit
- Ubuntu 12.04 64-bit
- Mac OS X 10.12.1

[Steps to reproduce]:
1.Launch Firefox using a new profile.
2.Open a new tab.
3.Click on the Pocket icon.

[Expected results]:
- The Pocket pop-up is displayed after clicking on the icon

[Actual results]:
- The user is redirected to the getpocket.com learn more web page.

[Additional notes]:
- This issue reproduces intermittently.
- This issue has been seen during the testing of  https://public.etherpad-mozilla.org/p/1344345
(Reporter)

Updated

a year ago
status-firefox52: --- → affected
status-firefox53: --- → affected
status-firefox54: --- → affected
Nate, not sure who to bug on your end about addon bugs, so you win :)

This sounds like it might be part of the a/b testing you added last year, would be good to verify.
Flags: needinfo?(nate)
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix

Comment 3

a year ago
Hey Shane,

You are correct! This is actually expected behavior that was introduced as part of our AB test for different methods of onboarding.
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox52: wontfix → unaffected
status-firefox53: affected → unaffected
status-firefox54: affected → unaffected
status-firefox55: affected → unaffected
Flags: needinfo?(nate)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.