Implement a doorhanger to notify Fission experiment users
Categories
(Firefox :: Messaging System, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox83 | --- | verified |
People
(Reporter: neha, Assigned: Yoric)
References
(Depends on 1 open bug)
Details
Attachments
(2 files)
Show a doorhanger to inform users that they have Fission enabled for those who get into the Fission Nightly experiment. We should show this only one time when it gets enabled for them for the first time, otherwise it might get annoying for the user. There should also be a link for 'Find more' and a close option.
The exact text for it can be discussed and decided.
Reporter | ||
Comment 1•4 years ago
|
||
Nika is working on another change for the prefs, building on top of kmag's changes in bug 1660057, so NI'ing her so she can coordinate with yoric.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
I think we should point to Fission wiki for the Find more link. Anny is also working on a blog so if that's ready in time, we can point to that.
Reporter | ||
Comment 4•4 years ago
|
||
Tim, can you point to someone to give some handy pointers to yoric for implementing this for Fission Nightly experiment users?
Assignee | ||
Comment 5•4 years ago
|
||
Comment 6•4 years ago
|
||
(In reply to Neha Kochar [:neha] from comment #4)
Tim, can you point to someone to give some handy pointers to yoric for implementing this for Fission Nightly experiment users?
:andreio is the tech lead for Messaging System and can help out yoric
Assignee | ||
Comment 7•4 years ago
|
||
Comment 9•4 years ago
|
||
bugherder |
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
bugherder |
Assignee | ||
Comment 12•4 years ago
•
|
||
@andreio, according to bug 1669497 apparently the doorhanger shows even when it shouldn't, so possibly when isFissionExperimentEnabled
is false
. Do you spot anything wrong, either here or on https://github.com/mozilla/messaging-system-inflight-assets/pull/156/files ?
Assignee | ||
Comment 13•4 years ago
|
||
Nika, could you double-check that I've understood correctly your instructions to implement isFissionExperimentEnabled
?
Comment 14•4 years ago
|
||
I'm going to follow up with QA and see if there's anything about targeting that can cause this. Since that is the only attribute in the targeting (and the code to expose it is trivial) I can't see any other reason where things could have gone wrong.
Comment 15•4 years ago
|
||
(In reply to David Teller [:Yoric] (please use "needinfo") from comment #13)
Nika, could you double-check that I've understood correctly your instructions to implement
isFissionExperimentEnabled
?
No, that attribute is incorrect. Services.appinfo.fissionExperimentStatus is an enum with integer values, and you're interpreting it as a boolean, which will produce incorrect results. Please change the code to instead check:
return Services.appinfo.fissionExperimentStatus == Ci.nsIXULRuntime.eExperimentStatusTreatment;
Assignee | ||
Comment 16•4 years ago
|
||
Gasp. I'm too used to strongly-typed languages.
(also, I feel stupid)
Thanks, Nika!
Comment 17•4 years ago
|
||
I am marking this as verified fixed based on the testing performed for PI-778 - QA sign-off for Fission experiment recipe. The complete list of bugs found during testing can be found here.
The experiment was tested using Firefox Nightly 83.0a1 (Build IDs 20201004212809 through 20201009041754) on Windows 10, Windows 7 and macOS 10.15.
Description
•