Inconsistent font sizes with force-device-scale-factor
Reported by
jleedev@gmail.com,
Dec 20 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36 Steps to reproduce the problem: 1. Set Windows scaling to 125% 2. Launch Chrome with --force-device-scale-factor=1 What is the expected behavior? Everything should be rendered at the default DPI, particularly fonts. What went wrong? Tabs have a larger font Window caption buttons are larger Scrollbars are larger Did this work before? N/A Chrome version: 57.0.2952.0 Channel: canary OS Version: 7 Flash Version: Coming from Issue 674585 , lots of users in the linked threads complain specifically about the omnibox being smaller and also mention that they're using force-device-scale-factor=1. This adds to the confusion as they are seeing a different picture than users with scaling turned off.
,
Jan 2 2017
,
Jan 3 2017
,
Jan 28 2017
force-device-scale-factor is a debug flag and we generally don't prioritize fixes to it, which is why I encourage people who want to make their Chrome window return to 100% scaling to set their Windows scaling to 100% globally. That said this is pretty irritating because it can make UI elements scale differently than normal, which disrupts debugging.
,
Feb 12 2017
This is disrupting my harmony work so I'm going to try fixing it.
,
Feb 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e commit 6cf3aecafe0e4790a0aa0dd8f44602acce121a2e Author: bsep <bsep@chromium.org> Date: Thu Feb 16 04:20:50 2017 Fix font sizes being incorrect when using --force-device-scale-factor. Normalizes font sizes received from Windows based on the unforced device scale factor, so that when they're scaled up later they end up the right sized for the forced scale. BUG= 675933 Review-Url: https://codereview.chromium.org/2695523002 Cr-Commit-Position: refs/heads/master@{#450869} [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/base/l10n/l10n_util_win.cc [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/base/l10n/l10n_util_win_unittest.cc [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/display/win/dpi.cc [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/display/win/dpi.h [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/display/win/screen_win.cc [modify] https://crrev.com/6cf3aecafe0e4790a0aa0dd8f44602acce121a2e/ui/display/win/screen_win.h
,
Feb 16 2017
,
Mar 18 2017
,
Apr 22 2017
Hello, this caused some problems for me so I opened issue 714365 . Unfortunately I don't have permissions that will let me CC or needinfo you. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hdodda@chromium.org
, Dec 27 2016Components: -UI Blink>Fonts
Status: Untriaged (was: Unconfirmed)