Chrome does not scale with DPI on Windows 7

RESOLVED WORKSFORME

Status

()

Core
Layout
--
major
RESOLVED WORKSFORME
7 years ago
2 years ago

People

(Reporter: Chris Cook, Unassigned, NeedInfo)

Tracking

({regression})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-CA; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.10 (maverick) Firefox/3.6.13
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-CA; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.10 (maverick) Firefox/3.6.13

I use Firefox 4 (currently beta 11) on my HTPC running Windows 7. Because it's an HTPC I have the UI scaled to 150% or even higher (my eyesight is poor). Most applications scale the interface to match the custom DPI (including Firefox 3.x) but the chrome in the recent betas does not scale. This includes the toolbars and the statusbar (when it's visible as with the download statusbar addon). I would expect both text and graphics for UI elements to scale but they do not.

In Firefox 4 beta 10 it seemed that the toolbar elements did scale but the icon/graphic did not. The back/forward buttons were as tall as the toolbar height (determined by text in the URL bar for example) but the icon was not proportionally larger and the icon was not larger so the button was not round.

Reproducible: Always

Steps to Reproduce:
1. Go to display settings
2. Set text size to "Larger - 150%"
3. Restart windows and Firefox 4b11
4. Observe that the toolbar is smaller than in other apps

Updated

7 years ago
Component: Theme → Layout
Keywords: regression
Product: Firefox → Core
QA Contact: theme → layout
WFM - @Reporter, if this still an issue for you, please state your current OS and Firefox version.
Version 	45.0
Build ID 	20160303134406
User Agent 	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Flags: needinfo?(beerfan)
Closing this as works for me, due to inactivity and lack of response to contradict comment 1. 
Feel free to reopen the bug and provide a test case if the issue still reproduces on a current build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.