Allow Chrome to render in scales other than multiples of 25% |
|||||
Issue descriptionWe added logic to round to multiples of 25% to prevent potential regressions with Windows Text Scaling enabled. In the past we have had problems scaling our browser to other than 125%, 150%, etc. Text Scaling can specify an arbitrary percentage. Very few of our users were using custom scale factors that weren't multiples of 25%, so this would affect fewer people. However, see issue #912140 - we do have a number of users who have custom scale factors. So we should at least try turning off the rounding, or at least providing a flag that turns it off and let people live with the results. We should prioritize this and decide where it goes in terms of development.
,
Dec 19
Forgot to add a reference: https://habr.com/post/412081/ (use google translate, if you don't understand Russian)
,
Dec 19
Comment 1 just for your hard work writing this , I hope that you will be heard.. I want to add that not only the letters-character appear smaller and hard to read but all the things like images and sites in general.. I use 132% scaling in my 1920x1080 resolution laptop but chrome does not respect that and appears as if the scaling is 125%.. things were perfect to 70 version and before .. I don't know what happent to 71 version and thing are messed up ..
,
Dec 21
,
Dec 21
,
Dec 21
,
Jan 10
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/eb0b5dd8dc6db45339a6c8b2850f7f19a9f38b44 commit eb0b5dd8dc6db45339a6c8b2850f7f19a9f38b44 Author: Dana Fried <dfried@chromium.org> Date: Thu Jan 10 23:47:53 2019 Relax x25% rounding requirement on browser scale factor. We originally put in this logic to prevent the use of the new Text Scaling/Text Zoom accessibility feature in the latest Windows 10 release from creating unusual scaling factors that we had not had the ability to fully test. However, we got a number of complaints from users who normally ran in custom scale factors on Windows (see issue #912140). Scale factors other than 25% do not seem to produce significant visual artifacts except slight (sub-pixel) aberrations at specific scale factors when there is a stroke around the active tab due to low theme contrast. Given some users' desire to see scale factors like 135% or 114% (which is evidently the default on at least one laptop model), this appears to be mostly win. We may have to do some pixel-pushing to be 100% visually polished if many users enable Windows Text Scaling accessibility feature, but from what I have seen those polish issues are likely to be rare and relatively minor. Bug: 916276 Change-Id: I5e49e8c06689d47a320d385c8b927665dbd51c3c Reviewed-on: https://chromium-review.googlesource.com/c/1388662 Reviewed-by: Robert Liao <robliao@chromium.org> Commit-Queue: Dana Fried <dfried@chromium.org> Cr-Commit-Position: refs/heads/master@{#621803} [modify] https://crrev.com/eb0b5dd8dc6db45339a6c8b2850f7f19a9f38b44/ui/display/win/screen_win.cc
,
Jan 11
Marking as fixed. Note that this will not fix the unsupported command-line flags (which are intended for internal/debugging use only). Chrome will also continue to respect the new Windows Text Zoom accessibility feature by scaling the entire browser. This only affects cases where the DPI + Text Zoom (if enabled) would produce a scale factor that is not a multiple of 25%; in that case, the exact scale factor will be respected instead of rounding to the nearest 25% as we did after adding Text Zoom support. Please report any visual artifacts resulting from odd scale factors as separate bugs. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xiamen...@gmail.com
, Dec 1971.0 KB
71.0 KB View Download
79.5 KB
79.5 KB View Download
79.5 KB
79.5 KB View Download