Scrollbars show through to GMail Context menus
Categories
(Core :: Layout: Scrolling and Overflow, defect)
Tracking
()
People
(Reporter: mkaply, Unassigned)
References
(Regression)
Details
(Keywords: regression, regressionwindow-wanted)
Attachments
(2 files)
On Windows and macOS, if the left sidebar rail in gmail has a scroll bar, it shows through the context menu displayed in gmail.
This doesn't happen in Chrome.
| Reporter | ||
Comment 1•3 years ago
|
||
| Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
On Windows11, I can reproduce this issue.
And the problem is gone if setting widget.windows.overlay-scrollbars.enabled to false.
On Ubuntu20.04, I can also reproduce this.
And the problem is gone if setting widget.gtk.overlay-scrollbars.enabled to false.
Comment 3•3 years ago
|
||
Regression window on Windows11:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3f8699724d492a8f00f7ad8d26b16c71236c311e&tochange=21553c91b278c428b4c8e861602a99fb1c1acc70
Updated•3 years ago
|
Comment 4•3 years ago
|
||
I ran mozregression on macOS, and can reproduce this on a 2022-04-04 build (20220404231805). On macOS, this only happens with overlay scrollbars, not "always visible" scrollbars. The regressor in comment 3 is correct as it seems to enable overlay scrollbars on Windows. but the issue itself is not new.
Comment 5•3 years ago
|
||
Regression window on Ubuntu20.04:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5e8914a02c20197917b5632a0d99cfaf9bc2e5ef&tochange=06e62c0f0b870617216e239b35fa88f1afda6b71
Comment 6•3 years ago
|
||
There is probably an existing issue on the z order of scrollbars but I can't find it right now, I know what change needs to be made, just need to read the history of the code to make sure it is correct and there is nothing depending on it.
Updated•3 years ago
|
Comment 7•3 years ago
|
||
(In reply to Timothy Nikkel (:tnikkel) from comment #6)
There is probably an existing issue on the z order of scrollbars but I can't find it right now
I think the bug you're looking for is bug 1803910.
| Reporter | ||
Comment 9•3 years ago
|
||
Yep, it's fixed.
Description
•