oshima, please triage.

#CBC-RS/TC-watchlist

This is WAI, assuming we implemented all features necessary?

The assigned owner "shihuis@chromium.org" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

So does the last comment mean no one is working on this bug now?  This is a critical accessibility feature for those using Android apps on high resolution displays as without it the user is forced to choose between a normal sized Chrome UI and tiny unreadable Android apps or a cartoonishly large Chrome UI with normal sized Android apps.

khmel@ - Please triage and assign appropriately

I think this should go to TOK team

+Laura as this was a feature that we worked with the accessibility team on.

The main change was for Android to respect the Chrome OS page zoom settings. Android UI should not be egregiously small compared to Chrome OS UI so would like to better understand the extent of the problem faced here. 

That may very well be the case for extreme resolutions such as those users setting the new Chrome Display Size to something like 50% on the Pixelbook as I can see in those cases things are not longer totally microscopic.  The problem is many users felt what Google considered to be proper size of Android apps is still too small at settings like 85% or what used to be 1350x900 or 1500x900 resolutions.  Being able to adjust this setting to Larger made everything finally the right size for both reading text and interacting with via touch.  I even see this issue on my older Chromebook 14 when sent to 100% or 115% as in both cases Android apps are still too small. Some people might disagree with me on this but considering how many people starred this feature when it was partially broken shows that it's still needed (https://bugs.chromium.org/p/chromium/issues/detail?id=739234). 

Quite simply Android apps and Chrome are just not sized the same way.  One is meant as a touch friendly interface (Android) and the the other is not even though it's making strides (Chrome).  It would therefore make sense there is no one size fits all for scaling and being able to control both separately needs to be maintained. Removing a feature people actively are using which for some can render Android apps unusable without blowing up the entire Chrome OS UI is not a smart plan.

Adding the conops Chrome OS hotlist for tracking.

Since Chrome 67 will be rolling out to the stable channel in a week and we just got a new beta that is still missing this feature should it just be assumed it is never coming back?

I need to stress again this is a critical usability feature for anyone that uses their Chromebook at a high resolution as Android apps do not scale the same as Chrome OS does.  I realize most Chromebooks have low resolution screens and therefore this doesn't matter to them however if Google really wants there to be higher end Chromebooks with high resolution displays this feature needs to be returned.

There are already 18 people starring this issue and it hasn't even rolled out to stable yet.  Please can someone address this?

Sorry for the delay. 

The change here to make the Android content display size to Chrome OS Setting's page zoom is a purposeful decision to reduce the discrepancies and align the experiences. Fundamentally, Android apps should respect Chrome OS preferences. Creating redundant and divergent options will not only create more confusion but also reduces incentives to create a cohesive experience. There's numerous upcoming Chrome OS improved touch experiences which should be reducing the existing gap. 

Making this closed as working as intended. 

I think you are confused to the nature of this problem.  Chrome OS scales as intended.  Unless Google has plans to force all Android app developers to allow for size controls within their apps including Google's own Android apps that feature is still needed.  Making Chrome OS more touch friendly is nice for users like myself who prefer to run at a higher resolution but it doesn't solve the fact that Android apps won't see any benefit to that and will still be too small to properly interact with as high resolutions like 1500x1000 on my Pixelbook or 1920x1080 on 1080P display Chromebooks.  

I am not saying we need this exact feature back as is but we need some sort of method to separately adjust Display Size for Android apps.  Like you said you want a cohesive experience but how is it cohesive when Android apps are too small to use or even see properly but Chrome OS is fine.  That is the opposite of what you are claiming Google wants here.  We don't even need the full on slider back, just the Large option from the slider as that is the only one I believe anyone was even using.  Just put a Large Android apps toggle in Display in the Chrome OS settings and default it to off.  I don't think this would add any confusion and would massively improve the functionality of Android apps running in Chrome OS with high res screens.

I agree with the previous comment, on my 15 inch chromebook (@1920*1080) I very much like the new display settings ChromeOS has provided which allow me to scale up the whole UI without it becoming fuzzy. I must be getting older or something but I like the 130% setting the best (just like I have my 15 inch windows laptop set at 125%). However, doing so makes all of the android apps appear fuzzy since, for some reason, they don't scale in the same way as the native Chrome OS UI. 
So I'm all for the new UI scaling introduced in Chrome 67 beta (I think it's awesome and really much better than the old method of reducing the screen resolution), however, please allow for separate scaling of the Android apps. For instance in the developer options of the android settings if you don't want to confuse people. Your aim is to create a cohesive experience, but for me the experience of using Android apps and the native browser is certainly not cohesive.

I agree with the previous 2 comments.

Any users with a high "Display Size"/resolution/DPI are effectively unable to use Android apps. Arguing otherwise is akin to saying "2+2=5" despite visual evidence that 2 rocks + 2 more rocks = 4 rocks.

Yes, unfortunately Google seems to only care about a cohesive Android experience for users of low resolution Chromebooks.  While I completely understand not wanting some secret unusual setting to control the scaling of Android app a setting is still needed.  Now that page zoom can control Android apps why not create a similar zoom setting just for Android apps.  After all I can set a global page zoom for all sites in Chrome and then adjust per site as needed within the browser.  Wouldn't that be just as uncohesive as you say a separate scaling setting for Android would be?

Now that Chrome 67 is rolling out to all users I feel this issue is only going to get more attention so please reconsider.

Ugh, it is extremely annoying that this accessability feature was removed.  Like many others have said simply having the LARGE option to scale Android apps would work fine.  

How does page zoom work with Android apps?  Is that like using CTRL+ or CTRL- on a Chrome window? 

THIS BUG SHOULD NOT BE CLOSED

I'm not sure why it was and it's frustrating that it seems a dev took about 2 seconds to look at and disregard the issue.

Yes, the scaling of the Android apps is changed with the scaling of ChromeOS but the two are starting from very different scaling.  When I say scaling I mean font sizing, mainly.

The screenshot attached is of the Android version of Excel.  I have my Pixelbook resolution set to 1500 x 1000 which is comfortable for me for ChromeOS but any Android app is far too small and difficult to read.  If I upscale the ChromeOS to compensate for Android apps then the fonts in ChromeOS itself are far to huge.

The fix previously was to use Android's Accessibility settings to scale just the Android apps.  Either bring that back or add a new ChromeOS feature to just affect the scaling of Android apps in ChromeOS.

Does anyone know how we get this ticket re-opened??

Deleted: Screenshot 2018-06-27 at 12.02.42 PM.png 708 KB

	Screenshot 2018-06-27 at 12.02.42 PM.png 708 KB View Download

I also agree that it's ridiculous a single dev can just decide a fault in how Android apps scale in Chrome OS isn't important enough to have a conversation on creating some kind of fix before closing a ticket that clearly impacts numerous users of Chrome OS, most notably the ones with high res displays which happen to be the most expensive ones. 

In regards to getting it re-opened maybe try reporting it to some of the tech blogs on how Google removed a highly useful accessibility feature that ultimately impacts users of their own $999+ Pixelbook the most. 

I know at least in my case my Pixelbook became significantly less usable with this feature removed as several Android apps are unusable when my Pixelbook is set at 1500x1000 most notably many of Google's own apps like Gmail and Google Calendar.

I wish we could put some work into harmonizing this for high resolution screens. I got a Pixelbook wanting a first party experience, but no matter how I try hacking a solution around it I can't seem to use Android apps properly.

Wait, why was a feature that was fixed in 65, removed in 67 with no alternative added to take its place?

Why not you know just restore the DPI setting that was removed without warning?

Unfortunately it seems that in the world of Chrome OS it is possible for a single dev to remove a feature that they deem to be unnecessary in spite of numerous requests in both this bug request and the one fixed for Chrome OS 65.

We can only hope that as more high resolution Chromebooks come out this year that professional reviewers will hammer Google for the poor sizing of Android apps vs native Chrome ones and this will get the attention of someone senior at Google who will force devs to bring back a solution to address the need for separate scaling of Android apps.

Add me to the users disappointed by the removal of this setting option. While I see the need to streamline settings between Chrome and Android to help the cohesive feel of what Chrome OS has become, but this shouldn't have been removed until Play apps respect the size UI sizing as the rest of the system.

Adding this example. Hangouts web on left and Android app on the right. 

Deleted: download_20180914_070054.jpg 257 KB

	download_20180914_070054.jpg 257 KB View Download

Another user disappointed by the removal of this setting option. Android app scaling is too small by default on Chrome OS! Please fix this and let us adjust the scaling for android apps! This is a crucial feature that strongly affects the user experience!

I'm yet another user who finds the removal of this setting very frustrating.  Older people such as I need font size control -- it's a basic *accessibility* requirement.

Should we just open a new ticket for this issue to get some attention again? Hopefully from a dev that can see the merit in at least restoring the original fix for those who need it, even if it is hidden in Android's accessibility features on chrome os.
Does anybody have any idea whether the upcoming move towards android 9.0 instead of 7.1.1 in chrome os will make a difference in this respect?

Not sure why this was removed. Using youtube on my pixelbook is a struggle with 90% or 100% display scaling. Scaling up means making ChromeOS pretty much unusable for me. Would really enjoy a fix for this.

> Application: Settings
> Activity: Vision Settings
> Package/Class: com.android.settings/com.android.settings.accessibility.AccessibilitySettingsForSetupWizardActivity
> --
> This information is exported by QuickShortcutMaker v2.4.0.
> https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut

...This is my workaround, Install QuickShortcutMaker, Create above shortcut, Star it, Open favorites tab, Try it:
Vision Settings / Display size / change from Default to Large (for my eyes)

This setting is persistent till restart.
Better to use this than disable Android apps in all my Chromebooks.

Deleted: Screenshot 2018-11-10 at 16.23.27.png 62.6 KB

	Screenshot 2018-11-10 at 16.23.27.png 62.6 KB View Download

I wonder if we just need to create another bug ticket for this? It seems despite a strong want for this feature to be restored this ticket appears to be permanently blocked by that one dev who has unilaterally decided to cripple Android apps on Chromebooks with high res displays.

I have to say the Google dev reaction to this bug ticket really makes me hope that Google gets a ton of returns of the Pixel Slate with people mentioning the non-matching scaling of Chrome OS and Android apps as a reason.

I have to add my two bits here. Using Chrome OS's default scaling settings on a Pixelbook and the Slack app has fonts too tiny for my eyes. I have to move closer to read well.

If this feature is not going to be restored, at least make the default font size for Android apps match the Chrome OS font size. I don't want extra configuration features. I only want readable text.

This issue highlights the ongoing consistency issue with the implementation of Android and Web apps co-existing on modern Chromebooks. Closing it without a proper solution shows a stunning lack of regard for creating a fluid OS and again shows that Google is oddly lacking in its attention to important UX details in OS development. It's exactly details like this that turn less tech savvy users off Chromebooks.

And why the heak was this closed? This is a perfectly good non intrusive feture

This bug ticket needs to be sent to all of the major tech blogs; Engadget, The Verge, Gizmodo, Ars Technica, etc... as with each passing day we get more horrible reviews for the Pixel Slate all complaining about the poor integration of Chrome OS and Android and this ticket pretty much sums up that Google doesn't care and it will never get better, especially when it seems the dev in charge of this also doesn't care. Consumers should be aware of this before wasting their money on an expensive product that will never get better.

The decision to remove the native ability of Android to set display and font size may actually be a violation of the law.

https://www.section508.gov/manage/laws-and-policies

Normally this does not affect the private sector, but if a federal agency uses devices affected by this it becomes a problem. The workaround provided in comment 33 above shows that the functionality is still there, just hidden. All we really need is to have this menu back, and to have the settings stick through a reboot.

Very disappointed access to this functionality has been removed. I agree with the intent behind making the scaling match between ChromeOS and Android, but the fact is that fonts in Android apps are currently too small. 

Independent scaling is also desirable within the built-in Linux environment.

See also: https://bugs.chromium.org/p/chromium/issues/detail?id=913228

I concur that this is something that needs addressing. I'm running Version 71.0.3578.94 (Official Build) (64-bit) and this is still an issue. Who get's to make the final call as to reopen defects? Is there a documented process for this?