Closed
Bug 1846803
Opened 2 years ago
Closed 2 years ago
Fix some remaining issues with micro survey feature callout experiments
Categories
(Firefox :: Messaging System, defect)
Firefox
Messaging System
Tracking
()
RESOLVED
FIXED
118 Branch
People
(Reporter: aminomancer, Assigned: aminomancer)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
- newtabFeatureCalloutCheck callouts don't correctly track their tour prefs, since the tour pref
browser.newtab.feature-tour
is not in SpecialMessageActions'allowedPrefs
- checkboxes and radios aren't the right width/height (fixed in bug 1846782, but that won't land till 118)
- the primary button transitions smoothly when it changes from disabled to active
- when clicking the primary button, its own
action
is replaced with an array of the active multi-select items' actions. which works for some cases, but in this case we want the primary button to set the tour pref AND do the action of the active multi-select item. we could add the set tour pref action to each of the multi-select items to work around this issue, but that's a lot of redundant code. it's better if we just append the multi-select items' actions to the clicked button's actions (if it has any).
Assignee | ||
Comment 1•2 years ago
|
||
Actually we don't need to fix #2 with feature changes. That will be handled in the experiment recipe.
Assignee | ||
Comment 2•2 years ago
|
||
- Allow messages to set
browser.newtab.feature-tour
- Prevent individual element transitions in feature callouts
- Change how multi-select item actions are processed so that, when
clicking the primary button, its action is performed as well as the
action of the selected item. - Remove some built-in styles that can be set by experiment recipe
- Allow messages to override the tour pref for newtab and pdfjs
Updated•2 years ago
|
Assignee: nobody → shughes
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•2 years ago
|
||
Comment on attachment 9347002 [details]
Bug 1846803 - Final adjustments to feature callout surveys. r=jprickett
Beta/Release Uplift Approval Request
- User impact if declined: We'll have to delay an experiment from 117 Beta to 118 Release.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1846557
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Just some small fixes to get an experimental feature working. The feature will only be enabled for a small audience of Beta users enrolled in an experiment. The Release audience won't be exposed at all.
- String changes made/needed:
- Is Android affected?: No
Attachment #9347002 -
Flags: approval-mozilla-beta?
Pushed by shughes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c2b5ba04825c
Final adjustments to feature callout surveys. r=jprickett
Assignee | ||
Comment 5•2 years ago
|
||
^ Regarding this uplift request, we also need to uplift bug 1846557 for the experiment. If it makes the uplift easier, I can provide a combined uplift patch. I figured it's probably better to keep the blame intact so we'll file separate uplift requests.
Comment 6•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
Comment 7•2 years ago
|
||
Comment on attachment 9347002 [details]
Bug 1846803 - Final adjustments to feature callout surveys. r=jprickett
Approved for 117.0b3.
Attachment #9347002 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Updated•2 years ago
|
status-firefox117:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•