Closed
Bug 1863507
Opened 1 year ago
Closed 1 year ago
Review Checker CFR is missing with a fresh app installation
Categories
(Fenix :: Shopping, defect, P2)
Tracking
(firefox119 disabled, firefox120 wontfix, firefox121 unaffected, firefox122 unaffected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox119 | --- | disabled |
firefox120 | --- | wontfix |
firefox121 | --- | unaffected |
firefox122 | --- | unaffected |
People
(Reporter: apetridean, Assigned: vdreghici)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid] [fakespot-android-mvp])
Attachments
(1 file)
6.12 MB,
video/mp4
|
Details |
Prerequisites
- Ensure your profile is clean.
- Access the debug menu and navigate to "About Firefox" -> Secret Settings -> enable Nimbus Preview Collection.
- Restart the application twice.
- Proceed to Nimbus Experiments -> Android Review Checker Beta Smoke Test on a testing branch.
Steps to reproduce
- Open the Firefox Beta app.
- Navigate to an Amazon product page.
- Observe the behavior.
Expected behavior
The Review Checker CFR is displayed when a user opens a PDP page.
Actual behavior
The Review Checker CFR is not displayed when a user opens a PDP page.
Device information
- Firefox version: Firefox 120.0b7
- Android device model and OS: Samsung GalaxyZ Fold 4 (Android 13), Google Pixel 7 Pro (Android 14), LG G7 fit (Android 8.1.0)
Any additional information?
The CFR reappears only after restarting the app or if I enter the settings menu and return to the PDP.
I could not reproduce this issue on the leatest Nightly 121.0a1 from 07.11.2023.
Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
status-firefox120:
--- → affected
Updated•1 year ago
|
Assignee: nobody → Vlad.DreghiciPopa
status-firefox119:
--- → disabled
status-firefox121:
--- → ?
Priority: -- → P1
Comment 2•1 year ago
•
|
||
Is this bug a regression from the recent CFR timing changes in bug 1861173?
Whiteboard: [fxdroid] [fakespot-android-mvp]
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Status: NEW → ASSIGNED
Updated•1 year ago
|
Priority: P1 → P2
Updated•1 year ago
|
Keywords: regression
Regressed by: 1861173
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1861173
status-firefox122:
--- → affected
Assignee | ||
Comment 4•1 year ago
|
||
After investigating this issue and comparing 120 with 121 I could not find what could possibly cause it and decided against trying to add a "speculative fix". Considering it is not reproducible in 121, I will mark this as WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•