Closed
Bug 1156918
Opened 9 years ago
Closed 9 years ago
Really wide (fat, large, giant) overlay scrollbars in today's nightly
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: mstange, Unassigned)
References
Details
(Keywords: regression)
Apparently this is a regression from bug 1139306.
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → Mac OS X
Hardware: Unspecified → All
Reporter | ||
Updated•9 years ago
|
tracking-firefox40:
--- → ?
Reporter | ||
Updated•9 years ago
|
Summary: Really wide (fat) overlay scrollbars in today's nightly → Really wide (fat, large, giant) overlay scrollbars in today's nightly, on retina / HiDPI displays
Comment 3•9 years ago
|
||
I backed out bug 1139306 from inbound because of this bug https://hg.mozilla.org/integration/mozilla-inbound/rev/799784735f9e
Comment 5•9 years ago
|
||
Fwiw I’m seeing this on a non-Retina screen as well (2012 MacBook Air 13").
Comment 6•9 years ago
|
||
Yes, I don't think this is Retina-specific. I have a fix in hand in bug 1139306.
![]() |
||
Comment 7•9 years ago
|
||
If you set ui.useOverlayScrollbars to 1 on Windows, you can reproduce this there as well. Requires a restart.
Comment 10•9 years ago
|
||
Also see it with an external 27" dell display. Removing the retina part from the title.
Summary: Really wide (fat, large, giant) overlay scrollbars in today's nightly, on retina / HiDPI displays → Really wide (fat, large, giant) overlay scrollbars in today's nightly
Comment 12•9 years ago
|
||
Since the regressing bug has been backed out, we removed the tracking for this bug. Is 40 still affected, should we clear that flag, as well?
tracking-firefox40:
? → ---
Flags: needinfo?(mstange)
Reporter | ||
Comment 13•9 years ago
|
||
Totally, this is fixed. Backout changeset is https://hg.mozilla.org/mozilla-central/rev/799784735f9e
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(mstange)
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•