Review Checker Blank Screen after filling out Satisfaction Microsurvey and Disabling Feature
Categories
(Firefox :: Shopping, defect, P1)
Tracking
()
People
(Reporter: jchen, Assigned: aminomancer)
References
(Blocks 3 open bugs)
Details
Attachments
(3 files)
STEPS TO REPLICATE
- You will need to use Review Checker by going to an Amazon, Best Buy, or Walmart PDP
- Opt in when you see the opt-in screen by hitting "Yes, try it"
- You'll need to fill out the Satisfaction microsurvey, which is triggered by being at least on your 2nd session and having already visited 5 PDPs that have available Fakespot Reviews Analyses on them. You can also simulate this experience by manually setting these preferences in about:config while testing:
browser.shopping.experience2023.survey.enabled must be true (experiment does this)
browser.shopping.experience2023.survey.optedInTime must be 24 hours ago (try 1696550403)
browser.shopping.experience2023.survey.hasSeen must be false
browser.shopping.experience2023.survey.pdpVisits must be 5
browser.shopping.experience2023.optedIn must be 1
- Complete the Satisfaction Microsurvey - you should be asked 2 questions, then you'll see a green confirmation message.
- Hit "Turn off Review Checker" to disable the feature (at any point after having filled out the survey)
- Navigate to another PDP
- Manually turn on Review Checker again from the Shopping Icon
EXPECTED:
- Review Checker should work as expected, you should be able to see an opt-in screen telling you about using the Review Checker
ACTUAL RESULTS
- See a blank Review Checker sidebar with only "Thank you for the feedback" in green, or if you dismissed that, then you should only see a blank screen in that sidebar where there normally would be content, with Review Checker as a title
ADDITIONAL NOTES
- The blank screen doesn't seem to happen if you hit X, the Shopping icon, or turn off Auto-Open to temporarily close out the Review Checker. It seems to only happen after you fill out the Microsurvey, and, at any point after filling out the Microsurvey, disable the Review Checker feature by clicking "Turn off Review Checker"
Assignee | ||
Comment 1•4 months ago
|
||
You actually don't have to fill out the survey. Just seeing the survey is enough. The problem is the survey is showing instead of the opt-in message, which is supposed to show because you're not opted in. We need to prevent the survey showing if the user is not opted in.
Assignee | ||
Comment 2•4 months ago
|
||
Updated•4 months ago
|
Comment 3•4 months ago
|
||
Per the conversation on phabricator, this doesn't need to block because we can roll out without a survey to 80%, then fix this post-initial-rollout and then run a survey in the held-back remainder.
Assignee | ||
Comment 4•3 months ago
|
||
[Tracking Requested - why for this release]: To make our US Review Checker rollout schedule, this fix needs to land in 128.0. Without it, we can't show an important survey to Review Checker users. The rollout will be holding at 80% enrollment so we can launch an extra holdback experiment that deploys the survey. So how long it takes the fix to ship to release users determines the length of time 20% of US users will go without Review Checker. The sooner this fix ships, the sooner we can launch the holdback experiment, the sooner we can ramp from 80% rollout to 100% rollout.
Comment 5•3 months ago
|
||
Tracking as requested, though note we are in the final week of beta for Fx128.
The last beta for Fx128 builds on 2024-06-28, and Fx128 goes to RC on 2024-07-01
Assignee | ||
Comment 6•3 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D212498
Updated•3 months ago
|
Comment 8•3 months ago
|
||
beta Uplift Approval Request
- User impact if declined: To make our US Review Checker rollout schedule, this fix needs to land in 128.0. Without it, we can't show an important survey to Review Checker users. The rollout will be holding at 80% enrollment so we can launch an extra holdback experiment that deploys the survey. So how long it takes the fix to ship to release users determines the length of time 20% of US users will go without Review Checker. The sooner this fix ships, the sooner we can launch the holdback experiment, the sooner we can ramp from 80% rollout to 100% rollout.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: In original revision
- Risk associated with taking this patch: Low
- Explanation of risk level: Behind a Nimbus experiment, and relatively low proportion of users can make it to the survey
- String changes made/needed: n/a
- Is Android affected?: no
Updated•3 months ago
|
Assignee | ||
Comment 9•3 months ago
|
||
The survey behaves oddly in verify mode on debug builds so I'm disabling the test in those conditions for now, due to the urgency. I'll continue looking into ways to make the test more stable and hopefully we can lift the restriction later on after the feature itself lands.
Comment 10•3 months ago
|
||
Backed out as requested by dev for causing a failure that went unnoticed.
Comment 11•3 months ago
|
||
Assignee | ||
Comment 12•3 months ago
•
|
||
Comment on attachment 9410020 [details]
Bug 1900486 - Re-render Review Checker messaging content when opt-in state changes. r=jprickett
beta Uplift Approval Request
- User impact if declined: To make our US Review Checker rollout schedule, this fix needs to land in 128.0. Without it, we can't show an important survey to Review Checker users. The rollout will be holding at 80% enrollment so we can launch an extra holdback experiment that deploys the survey. So how long it takes the fix to ship to release users determines the length of time 20% of US users will go without Review Checker. The sooner this fix ships, the sooner we can launch the holdback experiment, the sooner we can ramp from 80% rollout to 100% rollout.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: In original revision
- Risk associated with taking this patch: Low
- Explanation of risk level: Behind a Nimbus experiment, and relatively low proportion of users can make it to the survey
- String changes made/needed: n/a
- Is Android affected?: no
Comment 13•3 months ago
|
||
Comment 14•3 months ago
|
||
Backed out for causing mochitests failures in browser_shopping_survey.js.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/components/shopping/tests/browser/browser_shopping_survey.js | Uncaught exception in test bound test_onboarding_resets_after_opt_out - at chrome://mochitests/content/browser/browser/components/shopping/tests/browser/browser_shopping_survey.js:396 - TypeError: can't access property "wrappedJSObject", content.document.querySelector(...) is null
Comment 15•3 months ago
|
||
Comment 16•3 months ago
|
||
bugherder |
Updated•3 months ago
|
Comment 18•3 months ago
|
||
uplift |
Updated•3 months ago
|
Updated•3 months ago
|
Description
•