Add targeting in ASRouter for "colorways active" and "user has not set up colorways"
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox106 | --- | verified |
People
(Reporter: mviar, Assigned: mviar)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We'll need to be able to target messages based on whether or not colorways are active in for the initial feature callout tour in about:firefoxview
. We'll want to combine this with additional targeting for "user has not set up colorways" to target reminder callouts in bug 1786347.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Backed out for causing xpcshell failures test_backgroundtask_targeting.js
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | toolkit/components/backgroundtasks/tests/xpcshell/test_backgroundtask_targeting.js | test_targeting - [test_targeting : 16] 0 == 11
Assignee | ||
Comment 4•2 years ago
|
||
Thanks for flagging Cristian, sorry I missed this in the try push. I've addressed the issue and will attempt to re-land after my change is reviewed.
Assignee | ||
Updated•2 years ago
|
Comment 6•2 years ago
|
||
bugherder |
Comment 7•2 years ago
|
||
bugherder |
Comment 8•2 years ago
|
||
I have verfied this enhancement and I can confirm the following:
- The "colorwaysActive" and the "userEnabledActiveColorway" targeting parameters are successfully displayed in the ASRouter page.
- The "userEnabledActiveColorway" parameter is set to "true" if a colorway theme is enabled.
- The "userEnabledActiveColorway" parameter is set to "false" if a default theme is enabled.
Verified using the latest Firefox Nightly (106.0a1 Build ID - 20220829094551) installed on Windows 10 x64, macOS 11.6.5, and Linux Mint 20.2 x64.
Also, I have observed that the "userEnabledActiveColorway" parameter has no value if a custom theme is enabled, however, I have logged a separate issue for this scenario (see Bug 1787783 )
Description
•