Issue metadata
Sign in to add a comment
|
Chrome inconsistently resizes anchor font on Nexus 6P
Reported by
jdpic...@gmail.com,
Aug 26
|
||||||||||||||||||||||||
Issue descriptionDevice name: Nexus 6P Chrome version: 68.0.3440.91 Operating system: Android 8.1.0 URLs (if applicable): see attached html, or view the online demo here: http://jaydimock.com/menutest/index.htm Description: Using Nexus 6P device with Chrome browser, fonts in anchor tags are resized in a mysterious way (see attached screen shot). So far I've only been able to reproduce the issue on my Nexus 6P. Other Android devices I've tested are fine, as are iPhones. Neither does it happen on any desktop browsers (Firefox, Chrome, MS Edge, IE, Safari). Steps to reproduce: View the attached HTML (or online demo http://jaydimock.com/menutest/index.htm) in a Chrome browser on Nexus 6P. Expected result: All hyperlinks will have the same font size Actual result: Divs with class "menuGroup" containing more than 2 links display an unexpectedly small font size compared to fonts in divs containing only 1 or 2 links (see attached screen shot). To stop this from happening, you can add an empty div after every second anchor tag. It's a hack, but I couldn't find another way to fix the issue. To stop this from happening, you can add an empty div after every second anchor tag. It's a hack, but I couldn't find another way to address the issue.
,
Aug 29
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Navigated to http://jaydimock.com/menutest/index.htm and observed small font size in troubleshooting Chrome versions tested: 60.0.3072.0, 68.0.3440.91, 69.0.3497.53, 70.0.3534.0(Latest canary) OS: Android 9.0.0 Android Devices: Nexus 6p Issue is seen from M-60 older builds. Hence considering this issue as Non-Regression and marking as Untriaged. Please navigate to below link for log's -- go/chrome-androidlogs/877833 Thanks!
,
Sep 10
This is sadly working as intended. For mobile sites without a viewport chrome tries to resize text to improve legibility, this is a very inexact science and doesn't work quite as well as we'd like. The easiest way to fix this is to add a viewport declaration which will disable the auto-magic behavior.
,
Sep 17
I added a viewport meta tag and that did not make any difference. If you meant something else by a viewport declaration please elaborate. This is the meta tag: <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" /> Please re-open the bug. Also: I've confirmed the bug exists on Pixel 2XL as well.
,
Sep 17
I can reproduce this with the Pixel2 emulation using devtools. When I put "<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />" as the second tag on the page, below <html>, this goes away. Can you try again?
,
Sep 17
Reopening while waiting for feedback.
,
Sep 18
Aren't meta tags supposed to go inside the <head> rather than right after <html>? Anyhow, I tried putting "<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />" directly below <html>, and in a separate test, I put it directly below <head>. Both times, I was able to reproduce the issue on a physical Pixel 2XL device. I did not try it with an emulator but my guess is there's a difference between the emulator and the physical device, or else there's a difference between Pixel 2 (which you said you emulated) and Pixel 2XL. I viewed the file directly on my device this time rather than using the online demo (the demo uses a free hosting service which apparently adds some extra tags). I can confirm that viewing a locally downloaded file (attached) directly in chrome with a still results in this behavior on a Pixel 2XL device, with the viewport tag.
,
Sep 18
I've uploaded menutest2.htm for testing: https://877833.glitch.me I tested this with a Pixel 2 XL and I do not see the font size issue. I'm attaching a screenshot showing what I see. I tested Chrome 68 as well as Chrome 71. Is it possible that you've enabled accessibility settings (dots menu -> settings -> Accessibility -> Text scaling anything but 100%)? If so, that could cause this issue. If you are not able to reproduce with my url, but you could reproduce with your url, it's possible you were getting a cached result due to webserver settings. Can you try again using my url?
,
Sep 25
Tentatively closing due to lack of feedback, but I'm happy to re-open if needed.
,
Nov 12
Sorry for the late response. YES, my phone is set to larger than 100% font size. However, IMO this does not invalidate the issue. People who need larger font should still see that larger font in a consistent manner throughout the page.
,
Nov 12
Thanks for the response. I agree with you. I'll mark this as the same bug as 645717 for tracking purposes. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chelamcherla@chromium.org
, Aug 27