Tested the issue on Chrome Stable# 61.0.3163.98 / 62.0.3202.73 & Chrome Canary# 64.0.3251.0 on Pixel (Android 8.0.0 / OPR1 170623.027) and Pixel XL (Android 7.1.2 / N2G48E) and was able to reproduce the issue using the below steps --
1. Go to Accessibility -> Text scaling
2. Set it to max
3. Go to google.com and search for something

This is a Non-Regression Issue existing from M55 builds.
Please find the logs and screencast in the below URL --
go/chrome-androidlogs/777896


Note: Tested the same on Samsung J710 (Android 6.0.1) and could not reproduce the issue.
Thank You.

Over to Mobile team to clarify behavior changes between 6.0 and 8.0 with regards to text scaling as this is an android-only issue.

Apologies for the wrong url for logs and screencast. Please find the logs and screen cast in the below URL --
go/chrome-androidlogs/779409

ScreenCast has been provided for Android 8.1.0 on Pixel XL and Android 6.0.1 on Redmi Note 3.
Thank You.

Any updates? This is a major issue which makes Chrome unusable for people with imperfect vision.

 Issue 820061  has been merged into this issue.

Any updates with this issue?

 Issue 822527  has been merged into this issue.

 Issue 825096  has been merged into this issue.

 Issue 827177  has been merged into this issue.

The problem is that TextAutosizer will only scale some elements. For elements that don't qualify, it uses a 1.0f multiplier.

This is wrong. It should be using the accessibility scaling factor as the minimum multiplier value. (ie: 2.0f for 200%).

https://chromium.googlesource.com/chromium/src/+/32a7b19e92a9ff0fca3aba45c1fdd3896fdd5f1d/third_party/WebKit/Source/core/layout/TextAutosizer.cpp#445

https://chromium.googlesource.com/chromium/src/+/32a7b19e92a9ff0fca3aba45c1fdd3896fdd5f1d/third_party/WebKit/Source/core/layout/TextAutosizer.cpp#465


Or, possibly, use m_pageInfo.m_baseMultiplier

https://chromium.googlesource.com/chromium/src/+/32a7b19e92a9ff0fca3aba45c1fdd3896fdd5f1d/third_party/WebKit/Source/core/layout/TextAutosizer.cpp#544


See how Chrome on emulated Pixel 2 XL works properly while a Chrome on real Pixel 2 XL does not.

Deleted: emulated.png 977 KB

	emulated.png 977 KB View Download

Deleted: real-device.png 1.1 MB

	real-device.png 1.1 MB View Download

My previous comment referenced an older commit, but the issue is the same:

https://chromium.googlesource.com/chromium/src/+/746621834ade23fdb2623caac91563375c0d90ed/third_party/WebKit/Source/core/layout/TextAutosizer.cpp#436

 Issue 839178  has been merged into this issue.

Hi, 
Here is a friendly ping. is there any updates with this issue?

I learned recently that Firefox on Android has an option to scale text with AndroidOS font settings.

Safari on iOS has no problems using text scaling. In fact, it's not optional at all. It just follows the OS settings on text scaling (Dynamic Type).

The whole idea of using custom heuristics based on paragraphs is a poor one. There's no reason for Chrome to "be different". In the very least, the ability to render like every other browser should be an option on the screen (as Firefox is doing).

Adding UI>Accessibility component so that this is raised to the a11y team. Non-regression going back to M55 per comment above. It's a borderline feature request but I feel it is a bug. 

It is for the Chrome-specific feature and not related to any OS level feature. 

Chrome 72.0.3584.0 (Official Build) canary (32-bit)
OS: Android 7.1.1 Moto E4 phone with TalkBack 6.2.0.199837370

Steps to reproduce:
# Go to More options menu > Settings > Accessibility 
# Ensure text scaling is set to 100% default
# Close menu and back to any webpage with text such as https://en.m.wikipedia.org/wiki/Kiwi
# Examine size of text
# Go back to More options menu > Settings > Accessibility 
# Set text scaling to 200% (max)
# Close menu and go back to the webpage with text

Expected: text is now at 200% scale
Actual: text looks exactly the same as before 

You can also repro this on a variety of pages such as the NTP, Google Search results, the menus themselves, etc. 

 Issue 874631  has been merged into this issue.

Issue 841718 has been merged into this issue.

 Issue 890280  has been merged into this issue.

 Issue 710487  has been merged into this issue.

Issue 682371 has been merged into this issue.

 Issue 444853  has been merged into this issue.

I have duped many of the scaling not working bugs into this master bug. I then made the bug to solve the problem, 645717, blocking this bug. 

Bug 779409 (this one) consolidates all the user complaints about the feature not working 
Bug 645717 explores the solution to making text scaling work 

dmazzoni@ - is this supposed to have the UI>Browser component? It seems like an issue with scaling web contents.

Removing other components

I'm getting rid of a11y-required, I don't think this is a GAR bug