The header of the review checker sidebar does not remain in-view when scrolled
Categories
(Firefox :: Shopping, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | disabled |
firefox119 | --- | verified |
People
(Reporter: pmagyari, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-shopping])
Attachments
(1 file)
496.71 KB,
image/png
|
Details |
Found in
- Firefox 119.0a1 (2023-09-21)
Tested platforms
- Affected platforms: All
Preconditions
- browser.shopping.experience2023.enabled- "true"
- browser.shopping.experience2023.optedIn - "1"
Steps to reproduce
- Open Firefox Nightly.
- Navigate to an Amazon/Walmart/Bestbuy product page. (example)
- Click on the
Show more
button in the "Highlights from recent reviews" section of the review checker sidebar. - Scroll down inside the review checker sidebar.
Expected result
- According to the figma spec the header of the sidebar should remain in view regardless of the scroll position.
Actual result
- The header moves out of view as you scroll down.
Regression range
- Will return with a regression-range asap.
Updated•1 year ago
|
Reporter | ||
Comment 1•1 year ago
•
|
||
Mozregression returned the following pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c08cba545d2cfff90f54726bd536368b128cfb0b&tochange=a654205d84701ba611f22f0020be612e0db887c6
It seems like Bug 1852302 could be the culprit.
Niklas, could you take a look?
Thanks!
Comment 2•1 year ago
|
||
I think the patch in https://phabricator.services.mozilla.com/D188528 is fixing this?
I'm surprised that a regressor came up (I don't recall the header ever being in view when scrolling). Nonetheless, yes the patch Gijs linked is for Bug 1851839, which will keep the header stickied to the top.
Comment 4•1 year ago
|
||
:niklas, since you are the author of the regressor, bug 1852302, could you take a look?
For more information, please visit BugBot documentation.
Reporter | ||
Comment 5•1 year ago
|
||
I can confirm that this has indeed been fixed by the patch landed for Bug 1851839 so I'm closing this issue.
Description
•