Closed
Bug 1558968
Opened 5 years ago
Closed 5 years ago
Return to AMO is broken after Bug 1548697
Categories
(Firefox :: New Tab Page, defect, P1)
Firefox
New Tab Page
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | verified |
People
(Reporter: rrosario, Assigned: rrosario)
References
(Regression)
Details
(Keywords: github-merged, regression)
Attachments
(2 files)
There was a typo in the patch. From @andreio on Slack: "on line asrouter-content.jsx:301 the prop name should be bundles
not messages
it got changed in the latest fluent version"
Comment 1•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Iteration: --- → 69.3 - Jun 10 - 23
Comment 2•5 years ago
|
||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Keywords: github-merged
Resolution: --- → FIXED
Comment 3•5 years ago
|
||
Verified with latest Nightly on Win10x64 for the below scenarios:
- Force attribution from asrouter:
- set
browser.newtabpage.activity-stream.asrouter.devtoolsEnabled
totrue
,trailhead.firstrun.branches
as an empty string - restart browser - go to about:newtab#asrouter - Targeting - Force attribution - about:welcome => the RTAMO card is displayed
- End-to-end flow :
- install Firefox release from a
Get Firefox
button in AMO - launch browser then close it - check that thepostSigningData
file is created and contains the extension details - open a new Nightly profile - about:welcome => RTAMO card is displayed (more detailed steps can be found here
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Updated•5 years ago
|
status-firefox67:
--- → unaffected
status-firefox68:
--- → unaffected
status-firefox-esr60:
--- → unaffected
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
Updated•3 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•