Issue metadata
Sign in to add a comment
|
Recent changes to force-device-scale-factor ignore Windows font settings
Reported by
term...@gmail.com,
Apr 22 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: 1. Windows 7 x64 125% Display 2. Control Panel > Personalization > Window Color > Advanced Appearance Settings > Increase the font for both Message Box (eg Tahoma 13) and Menu (Arial 12). Apply. 3. Restart Chrome with --force-device-scale-factor=1 and observe Chrome does not respect font sizes. What is the expected behavior? Like every other application Chrome should respect fonts and sizes that I set in Windows. I'm using force device scale because of https://bugs.chromium.org/p/chromium/issues/detail?id=410696#c46 What went wrong? Broken when I recently upgraded Chrome stable. Bisected to issue 675933 . You are probably looking for a change made after 450868 (known good), but no later than 450872 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/be2c7115703a6610b25128809eb388ac28d07285..4807ace9c09bd194d2b453d9cab1689383539923 Did this work before? Yes Chrome version: 58.0.3029.81 Channel: stable OS Version: 6.0 (Windows Vista, Windows Server 2008) Flash Version:
,
Apr 24 2017
@bsep: Could you please look into this issue.
,
Apr 24 2017
I'm experiencing the exact same problem. There is an on going discussion on Reddit about this: https://www.reddit.com/r/chrome/comments/66dyrj/text_smaller_after_chrome_58_update/ Please fix this issue in the next update. It would be greatly appreciated.
,
Apr 26 2017
Chrome does respect font size changes, even with the force-device-scale-factor flag. The browser must be restarted after applying the changes. See attached screenshots, with the menu/message box fonts set to 11/12 in the "normal" case and 17/18 in the "large" case, with --force-device-scale-factor=1. The flag doesn't do anything special with system font sizes. There are some cases where Chrome does not respect custom font sizes, but those are being tracked elsewhere (for example, the omnibox is tracked in bug 260766). Yes, the font size did decrease when using force-device-scale-factor after the linked patch, but it was too large before, and now it's correct. When I say "correct" I mean it looks more similar to Chrome's appearance at 100% native scaling. It was changed because the flag is intended as a convenience for development and the incorrect font size was interfering with our productivity.
,
Apr 26 2017
,
Apr 26 2017
Ok thanks for your reply. I meant basically I wanted it to use my appearance settings. To me that is what is correct. I appreciate what you are saying though about it being a developer option. The problem as I've noted in some other bugs is when I run Chrome without ClearType or font smoothing in Windows 7 at 125% the font spacing is sometimes off unless I use --force-device-scale-factor=1. Even with that the location bar text is still small. I read in the reddit thread today there is also --device-scale-factor=1 and for right now at least that is working the way --force-device-scale-factor=1 used to.
,
Apr 26 2017
Issue 715668 has been merged into this issue.
,
May 4 2017
I describe better in Issue 718590 .
,
Jun 23 2017
I have this same problem since I upgraded the Windows 10 to Windows Creator. My brower's bookmarks, and tabs are now not in a bold font nor are they large enough to read. Neither can I read notification boxes in the bottom right corner. How can I fix this? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Apr 24 2017