[mac] Scroll bar disappear on scrolling inside bookmarks and history menus (with permanent scroll bar turned on in system preferences)
Categories
(Core :: Web Painting, defect)
Tracking
()
People
(Reporter: cfogel, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(4 files)
Affected versions
- 74.0a1(20200107215758), 73.0b2
Affected platforms
- mac OS 10.12, macOS 10.15
Steps to reproduce
- Launch Firefox (have bookmarks/history on the profile - can be imported from other browsers);
- Click on the View history, saved bookmarks and more button;
- Click on either Bookmarks or History option from the dropdown menu;
- Hover over the first menu option and scroll all the way down;
Expected result
- no glitches occur;
Actual result
- scroll bar is no longer fully displayed;
Regression range
- will look into it and provide one asap;
Additional notes
- attached recording with the issue;
- issue can be reproduced by grabbing and dragging the scroll bar as well.
Comment 1•5 years ago
|
||
Will wait on regression range but, Gijs do you have any thoughts? Has anything changed with this menu recently?
I notice when reproducing locally that the height of the list tends to get misaligned with the bottom of the scrollbar as well. It jumps back to the correct height on subsequent scroll events whenever a re-layout happens.
Updated•5 years ago
|
Comment 2•5 years ago
|
||
I can't think of anything that's changed in this department on the front-end side for a while now. Will keep needinfo to see if I can come up with something... Cristian, do you know if 72 / release and ESR are affected?
Reporter | ||
Comment 3•5 years ago
•
|
||
Using mozregression on macOS 10.13.6 managed to get the following pushlog:
- URL;
- most likely culprit seems to be bug 1505582.
Updating flags for RC 72.0.1, 68.4.1esr as well.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Comment 4•5 years ago
|
||
So does this not reproduce on 10.13 or 10.14 ? Only 10.12 and 10.15 ? That's... peculiar. Because the change in the regression window only changed the translucency of the background of the entire panel. I wouldn't have expected that to make any difference...
Reporter | ||
Comment 5•5 years ago
|
||
Ah, I can see your point. Might have been confusing with mentioning it as such.
It reproduces on all our available mac OS versions.
Comment 6•5 years ago
|
||
Seems this only reproduces with permanent scroll bars enabled.
I know very little about graphics/layout, but I can only imagine that the change to the background colour somehow made a difference in how layers etc. are computed and that's how that CSS change was able to trigger this bug?
Comment 7•5 years ago
|
||
Cristian, can you try with the layout.css.cached-scrollbar-styles.enabled pref set to false? That feature introduced a couple of regressions with scrollbar styling.
Reporter | ||
Comment 8•5 years ago
|
||
Same result with the pref set to false.
Updated•5 years ago
|
Comment 10•5 years ago
|
||
@Matt: Any thoughts on the theory in comment 6 that might lead us in the right direction?
Comment 11•5 years ago
|
||
Could reproduce the issue on Mac 10.14.6 with Firefox Nightly 75.0a1 (2020-02-13) with and without the pref from comment #7 set to false. Will add the according flag.
Comment 12•5 years ago
|
||
I can't reproduce this unfortunately.
It looks like it could be some sort of painting/sorting issue though, so next steps might be to collect a display list dump and see if the scrollbars are present or not (and in the right z order).
Updated•5 years ago
|
Comment 13•5 years ago
|
||
I can still reproduce this reliably in Nightly 76.
Miko: Might you be able to help diagnose (see comment 12)? Will get someone from layout to help as well.
Updated•5 years ago
|
Comment 14•5 years ago
|
||
(In reply to Cristian Fogel, QA [:cfogel] from comment #3)
Using mozregression on macOS 10.13.6 managed to get the following pushlog:
- URL;
- most likely culprit seems to be bug 1505582.
Updating flags for RC 72.0.1, 68.4.1esr as well.
I can confirm that this is the regressing patch. Backing it out locally fixes the issue. I am still investigating what the root cause is.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 15•5 years ago
|
||
Comment 16•5 years ago
|
||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Hi Markus - Just curious if there's any update on this. Is this definitely an issue on the painting side of things?
Updated•5 years ago
|
Comment 18•2 years ago
|
||
I don't remember.
Description
•