Open
Bug 986010
Opened 11 years ago
Updated 3 years ago
Fix up hard coded pixel values in nsNativeThemeWin for high-dpi
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
NEW
People
(Reporter: jimm, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [win:sizing])
nsNativeThemeWin has a lot of hard coded pixel values. I recently fixed some related to menu arrows in bug 911409, but there are many more particularly in GetWidgetPadding and GetMinimumWidgetSize. I think we can keep most of these consts, they've been tweaked over the years to look right @ 96 dpi. But we should adjust the actual values we return based on the dpi scale factor so things look the same on higher dpi systems.
|
||
Comment 1•11 years ago
|
||
Be careful since some UI elements (like buttons) are nine sliced for high DPI so certain paddings don't actually scale linearly.
|
Reporter | |
Comment 2•11 years ago
|
||
(In reply to Greg Edwards from comment #1)
> Be careful since some UI elements (like buttons) are nine sliced for high
> DPI so certain paddings don't actually scale linearly.
what do you mean by "nine sliced"?
|
|
||
Comment 3•11 years ago
|
||
|
|
Reporter | |
Updated•11 years ago
|
Assignee: jmathies → nobody
|
||
Updated•3 years ago
|
Whiteboard: [win:sizing]
|
||
Updated•3 years ago
|
Severity: normal → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•