New issue
Advanced search Search tips

Issue 820443 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome app mode uses low-resolution (small?) icon for app (taskbar) icon

Reported by adam.str...@java.pl, Mar 9 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
1. Use some Windows machine with HiDPI display, e.g. laptop with HiDPI display set 200% scaling (it has to be at least 125% scaling so the problem is visible)
2. Launch some website with at least 64x64 favicon in app mode, e.g. jupyter.org:
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --app=https://www.jupyter.org/
3. Chrome app first is spinning (NOTE: spinner is also low-quality on HiDPI display)
4. Once loaded Jupyter icon is set, however the icon has low-quality - visible jaggies from upscaling

What is the expected behavior?
http://jupyter.org/favicon.ico is 64x64 and this icon should be used for taskbar, downscaled if needed.

What went wrong?
It seems that 32x32 icon is upscaled to target resolution, e.g. 64x64 (200% DPI), causing blurry icon with jaggies.

NOTE: This is aesthetic nuance, but becomes obvious when more and more HiDPI screens are used.

Did this work before? N/A 

Chrome version: 64.0.3282.186  Channel: stable
OS Version: 10.0
Flash Version: 

Reference for application icons depending on DPI setting:
https://msdn.microsoft.com/en-us/library/ms701681%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
 
Labels: Needs-Triage-M64
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Feedback
adam.strzelecki@ Thanks for the issue.

Tested this issue on Windows 10 HiDPI system on the reported version 64.0.3282.186 and the latest canary 67.0.3368.0 by following the below steps.

1. Set the system scaling to 200%.
2. Launched the website jupyter.org in Chrome from command line in app mode.
3. While the website is loading couldn't observe any blurry spinner and once the website is loaded, the app icon on the taskbar is clear and not observed to be blurry.
Attached is the screen cast for reference.

Request you to please check and confirm if anything is missed from our end in triaging the issue.

Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..
820443.mp4
2.2 MB View Download

Comment 3 by adam.str...@java.pl, Mar 13 2018

Susan, I looked at your movie, and if you look closely spinner (loading) icon and final Jupyter icons are definitely not clear - they are blurry (low resolution) icons. The problem is that you need to look at the taskbar at full-resolution, but this movie shows a whole desktop, so if you play it - most players won't let you zoom into this particular region of interest.
Please see attached static shots of 820443.mp4 attached to this comment that I have generated cropping your movie with ffplay.

Just as an additional proof I am attaching 200% DPI scaling screenshots of my Win10 taskbar below as well, when you can see that used icon is definitely not 64x64, but some low resolution.

My whole point is that Chrome app mode is not using best available icons, but probably only fixed size of 32x32, which may work well only on conventional 72-96 DPI displays.
JupyterOrgLoading.png
43.0 KB View Download
JupyterOrgLoaded.png
45.9 KB View Download
Resolution.png
7.6 KB View Download
820443mp4-Capture-1.png
24.2 KB View Download
820443mp4-Capture-2.png
32.8 KB View Download
820443mp4-Capture-3.png
143 KB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 13 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment