New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 686151 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Notification icon is scaled with artifacts on HiDPI screen

Reported by yan.mosy...@gmail.com, Jan 27 2017

Issue description

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

Steps to reproduce the problem:
1. Trigger a Chrome notification. For example, use this extension: https://chrome.google.com/webstore/detail/notification-api-sample/cndmbddaappldijonoekcdfdlhemhejm/related

What is the expected behavior?
The icon of the notification (displayed in the left part) is scaled properly without noticeable artifacts

What went wrong?
Scaling artifacts are seen.

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

This is observed with website notifications as well.
 
notification.png
4.9 KB View Download
Labels: Needs-Triage-M56
Labels: Prestable-56.0.2924.76
Cc: krajshree@chromium.org
Components: Platform>Extensions>API
Labels: Needs-Feedback
Unable to reproduce the issue on Win-10 (High DPI: having devicepixelratio=2.5) using chrome reported version #56.0.2924.76 and latest canary #58.0.2996.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Added "notification API sample" app by navigating to URL: https://chrome.google.com/webstore/detail/notification-api-sample/cndmbddaappldijonoekcdfdlhemhejm/related
2. Clicked on the app and then clicked on the basic notification button.
3. Observed that The icon of the notification is scaled properly without noticeable artifacts as expected(as in the attached screenshot).

Reporter@ - Could you please check this issue on latest canary #58.0.2996.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

686151.mp4
667 KB View Download
Hi. I was able to reproduce the issue in latest Chrome Canary build as well. Version string: 58.0.2997.0 (Official Build) canary (64-bit).

Windows 10 build 14393.693. Scaling is enabled and is at 125%.

Please see attachment. Thanks.
notification_with_chrome_about.png
62.5 KB View Download
Labels: -Needs-Feedback Needs-Bisect
Labels: Pri-1
Cc: rbasuvula@chromium.org
Labels: -Needs-Bisect -Needs-Triage-M56
Status: Untriaged (was: Unconfirmed)
Tested the issue on chrome Stable #56.0.2924.76, Canary 58.0.2997.0 in Windows 10.0 and was able to reproduce the issue.

This is a Non-Regression issue since seeing this from M35 #35.0.1898.0, Making the status to Untriaged so that the issue would get addressed.

Note : Not Able to reproduce the issue in MAC 10.12.2 and Linux Ubuntu 14.04.

Thank you.

Cc: bever...@google.com
Owner: dewittj@chromium.org
Status: Assigned (was: Untriaged)
Assigning to dewittj@ for notifications API traige; +beverloo@ FYI.
I believe the image used in that extension is 64x64 which isn't likely to scale all that well to the 80x80 (or 160x160) size of the actual view.

OP, are you mostly asking for higher-quality scaling algorithms?  I think generally the answer has been to supply proper size resources for best results.
Cc: -bever...@google.com peter@chromium.org
Components: -UI UI>Notifications
@c9 Yes, I'm talking better scaling algorithm. Originally, I noticed this issue with a facebook.com notification where a Facebook logo had noticeable jagginness around the sharp areas of the image.

My opinion is even if there's a guidance to use resources of proper size it's better to have a smoother (sorry for the pun) fallback in case when the resources for some resolution scenario are lacking.

Comment 12 by awdf@chromium.org, Sep 8 2017

Status: WontFix (was: Assigned)
Hi Yan, thanks for the bug report and suggestion to use a higher quality scaling algorithm. However, we are already using our 'RESIZE_BEST' algorithm to display these images (see https://cs.chromium.org/chromium/src/ui/message_center/views/proportional_image_view.cc?type=cs&q=resize+f:message_center&sq=package:chromium&l=38), which optimizes for high quality scaling. The primary cause for this bug is the extension providing an image that is too small - a 64x64 image for display at 80x80/160x160.

Sign in to add a comment