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

Issue 638810 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ brajkumar@chromium.org
peter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Push Notification, After chrome version 52 updates , not getting the icon in the notification

Reported by kjanilku...@gmail.com, Aug 18 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Subscribe to any of the push notifications in previous versions of chrome,
2. Wait for the notification , you can see the icon.
3. now update the chrome notification to 52 or recent versions, now when you receive a notification you can't see the icon in the push notification received

What is the expected behavior?
It should icon in the push notifications

What went wrong?
 Subscribe to any of the push notifications in previous versions of chrome,Wait for the notification , you can see the icon. now update the chrome notification to 52 or recent versions, now when you receive a notification you can't see the icon in the push notification received, in previous versions of chrome this is working fine

Did this work before? Yes In previous version of chrome

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

can i know whats the issue, is it related to my code or any thing happening with the chrome recent updates
push-notification-v51.png
74.7 KB View Download
push_notification-chrome-v52.png
26.5 KB View Download
IMG_Notification_Chrome-V51.png
27.4 KB View Download

Comment 1 by brajkumar@chromium.org, Aug 18 2016

Cc: brajkumar@chromium.org
Components: UI>Notifications
Labels: Needs-Feedback
Unable to reproduce the issue on Windows-10 using chrome latest stable M52-52.0.2743.116 by following steps mentioned in the original comment. Observed the icon in the  push notification is displayed as expected even after upgrading chrome from earlier to latest version of M52.

kjanilkumar@ - Could you please confirm is this issue is seen across all sites notification or specific to yatra sites? Please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser. Attaching screen-cast from our end, please have a look on it and let us know if we are missing anything from our end.

Thanks!
Recording #11.mp4
10.3 MB View Download

Comment 2 by kjanilku...@gmail.com, Aug 18 2016 

This issue we had seen in the latest browsers only, cross checked this on other systems also, not sure wether this is with chrome recent update or whats happening , as we didn't do any code changes on worker.js recently,if you can help us in trouble shooting this issue that would be greatfull
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 25 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 4 by awdf@chromium.org, Sep 14 2016 

Hi there kjanilkumar

To confirm, do you only have the issue with notification icons not displaying on buzz.grabon.in, or do they also not display on other websites, such as https://tests.peter.sh/notification-generator/ ?

Please find our latest developer instructions for displaying push notifications at https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web?hl=en .

Thanks.

Comment 5 by brajkumar@chromium.org, Jan 20 2017

Labels: -Needs-Review Needs-Feedback
Owner: ----
kjanilkumar@ Could you please respond for the comment #4 

Thanks!

Comment 6 by peter@chromium.org, Jul 4 2017

Status: WontFix (was: Unconfirmed)
I'm going to assume this no longer is an issue.
►

Sign in to add a comment