UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36 Example URL: http://web.mit.edu/andersk/Public/font-size-css-units.html Steps to reproduce the problem: 1. Visit http://web.mit.edu/andersk/Public/font-size-css-units.html 2. At 100% page zoom, observe that all the lines are roughly the same size. 3. Zoom in. What is the expected behavior? All lines should get bigger by the same ratio. What went wrong? The lines where font-size is measured in ex or ch get bigger much faster than the other lines. At 500% page zoom, they are shown at 25 times their original size. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 37.0.2062.94 Channel: beta OS Version: Flash Version: Shockwave Flash 14.0 r0 I’m using 200% default zoom as a workaround for missing high-DPI support on Linux, so this makes some pages look really odd. I first noticed it on https://fedoraproject.org/wiki/Changes/CryptoPolicy.
Sep 1 2014,
Sep 3 2014,
Able to reproduce the issue on Mac and Linux. This is a non-regression from M24 24.0.1312.57 (Official Build 178923) chrome versions to latest canary 39.0.2144.2.
Oct 10 2014,
Moving all non essential bugs to the next Milestone.
Nov 17 2014,
This issue has already been moved once and is lower than Priority 1,therefore removing mstone.
Jan 9 2015,
Migrate from Cr-Blink-Rendering to Cr-Blink-Layout
Jan 4 2016,
May 23 2016,
Jul 11 2016,
We recently ran into this bug in MathJax, cf. https://github.com/mathjax/MathJax/issues/1438. Due to this bug, we have to resort to measuring the surrounding font (to match the x-height with a webfont) instead of just using a suitable ex-height. It would be great if this was fixed. FWIW, FF and IE/Edge handle this fine.
Jul 11 2016,
Apr 5 2017,
Confirm that this bug exists even now, with Chrome's HiDPI support. (using --force-device-scale-factor=2). Happens with both the the test page and the Fedora project wiki page listed in the examples in Comment 1.
May 1 2018, Project Member
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
May 1 2018,
FWIW, the problem is still present (current Chrome 66).
May 2 2018,
Issue 928036 has been merged into this issue.
Sign in to add a comment