Return-to-AMO about:welcome shows Trailhead cards and triggers experiments
Categories
(Firefox :: Messaging System, defect, P1)
Tracking
()
People
(Reporter: Mardak, Assigned: k88hudson)
References
Details
(Keywords: github-merged)
Attachments
(5 files, 2 obsolete files)
If trailhead state thinks it's something other than control, return-to-amo showing cards after the initial screen might pick up trailhead cards.
| Reporter | ||
Comment 1•7 years ago
|
||
At latest, we'll need this for when we turn on experimentation, but better to get in to nightly 68 for earlier testing
| Assignee | ||
Updated•7 years ago
|
| Reporter | ||
Comment 3•7 years ago
•
|
||
STR:
- Ensure
trailhead.firstrun.branchesis set to blank / no string value (to enable experimentation, and restart when changing) - Trigger usual return-to-amo (e.g., about:newtab#devtools -> Targeting -> Attribution Parameters -> Force Attribution)
- Go to about:welcome (should see return to AMO)
- Click "Get Started…" to see cards
Expected:
Cards show the usual RTAMO cards instead of Trailhead cards
Actual:
Trailhead cards shown (attachment 9065408 [details])
| Reporter | ||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Comment 6•7 years ago
|
||
| Reporter | ||
Comment 7•7 years ago
|
||
Comment 8•7 years ago
|
||
I've verified this in Nightly 69.0a1 (latest) and in Beta 68.0b4 with Win10x64 and macOS High Sierra 10.13.6 by following the provided STRs.
While testing, I've run into the following issue: when I open about:welcome after having Forced attribution, the RTAMO overlay is not loaded and a blank page is displayed instead. I've attached a video that shows the issue.
Not sure if significant, but when I'm editing trailhead.firstrun.branches to "" I receive the following warning in the console:
LoginHelper: Couldn't parse origin for about:config
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.displayHostPort]", result: 2147500037, filename: "resource://gre/modules/LoginHelper.jsm", lineNumber: 219, columnNumber: 0, data: null
Another question: Comment 7 mentions that 67.0.5 should be fixed, however, If I follow the link to the corresponding build, I'm getting results for 67.0.1.
Comment 9•7 years ago
|
||
Comment 10•7 years ago
•
|
||
I can confirm the issue. Loading about:welcome correctly triggers the RTMO message, on component mount it calls triggerOnboarding [0] which in turn causes a new type of overlay message to be set invalidating the RTMO overlay. Not sure yet what caused the regression but I'm looking into it for a fix.
The triggerOnboarding call is required to render the regular onboarding cards in the background (behind the RTAMO) message.
Comment 11•7 years ago
|
||
Issue is caused by the updated targeting for the ONBOARDING_3 message (trailheadInterrupt targeting doesn't match). But if setupTrailhead is called you won't into the problem.
Conclusion: In order to test the different onboarding flows new profiles have to be created each time. Simply changing trailhead.firstrun.branches is not enough to reset the various configurations of the Trailhead experiment.
Comment 12•7 years ago
•
|
||
I'm not sure I understand what should be the proper way to verify this fix. I have run two scenarios:
- Conditions to trigger RTAMO flow
- create a new profile with the latest Nightly
- open
about:configand setbrowser.newtabpage.activity-stream.asrouter.devtoolsEnabledtotrue - go to about:newtab#devtools -> Targeting -> Attribution Parameters -> Force Attribution
- open about:welcome --> here I should see the RTAMO overlay, but I see the Trailhead card instead. The RTAMO overlay is displayed only after I'm restarting the profile
- click on
Get started with Nightlyin the RTAMO overlay--> the RTAMO onboarding card is displayed but it doesn't look like the original rtamo onboarding (see attachments rtamo onboarding cards.gif and original rtamo onboarding)
- Same steps as above, but with
trailhead.firstrun.branchesset to""
- triggeres the issue described in Comment 8
Please clarify which are the correct STRs for verifying this fix
Thanks
Comment 13•7 years ago
|
||
Comment 14•7 years ago
|
||
| Reporter | ||
Comment 15•7 years ago
|
||
Sorry, I meant to say set the pref trailhead.firstrun.branches value to be blank / empty string, so delete the whole entry or set the value to be nothing.
| Reporter | ||
Comment 16•7 years ago
|
||
Comment 17•7 years ago
|
||
Verified fixed on latest Nightly and Beta 68 with Win10x64 and macOS High Sierra 10.13.6.
The issue I've mentioned in Comment 8 was happening because I was setting trailhead.firstrun.branches to "" , as mentioned in the STRs. In order for the fix to work the value for trailhead.firstrun.branches should be left empty.
I've attached a video showing that the correct rtamo cards are displayed.
Comment 18•7 years ago
|
||
| Reporter | ||
Updated•7 years ago
|
Description
•