Issue metadata
Sign in to add a comment
|
Notification with requireInteraction option is not displayed
Reported by
ur...@yahoo-inc.com,
May 24 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3109.0 Safari/537.36
Steps to reproduce the problem:
1. Go to any website
2. Allow the browser to display browser Notifications for that website
3. Open the console and enter:
new Notification('You have new notifications.', {icon: 'https://s.yimg.com/rz/uh/notifications/default-notif-img.png', requireInteraction: true})
What is the expected behavior?
A notification should be displayed.
What went wrong?
Seems like a regression got introduced where when attempting to display a Notification using `requireInteraction: true` option. Using `requireInteraction: false` or removing the option, will display the Notification.
Did this work before? Yes Version 58.0.3029.110 (64-bit)
Does this work in other browsers? Yes
Chrome version: 60.0.3109.0 Channel: canary
OS Version: OS X 10.12.4
Flash Version:
I observed the behavior on Chrome Version 60.0.3109.0 (Official Build) canary (64-bit) on Mac OS 10.12.4
,
May 25 2017
Unable to reproduce the issue on Mac-10.12.4, Windows-7 and Linux Ubuntu-14.04 using chrome stable version 58.0.3029.110 and canary 60.0.3109.0 with the steps mentioned on comment#0. Please find the attached screen cast and let us know if anything missed here to reproduce the issue. Thanks.
,
May 25 2017
Notifications that require interaction are displayed as an alert through an XPC service rather than by the Chrome process itself. In the notification center options, can you confirm that all Chrome entries are enabled to show notifications? The bundle name for our XPC service on Canary is identical to those on the release channels, so please consider Stable/Beta/Dev (whichever is applicable) as well. (We're fixing this.)
,
May 25 2017
Thanks for promptly looking into this Suresh and Miguel. I've checked the Notification Center and both of them are enabled to display alerts, attaching screenshots and the screencast of how we are observing the issue. (I've been able to reproduce on 4 machines so far).
,
May 25 2017
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 26 2017
Somehow unable to reproduce the issue on Mac-10.12.4, Windows-7 and Linux Ubuntu-14.04 using chrome stable version 58.0.3029.110 and canary 60.0.3111.0 with the steps mentioned on comment#0. Could someone from UI>Notifications team please look into this issue as the issue is not reproducible from our end. Removing Needs-bisect label as of now. Thanks.
,
May 26 2017
Yes, this is a regression specific to canary. Dev/Beta and Stable should still be fine. We are working on it.
,
Jun 10 2017
Canary was left in an interim state for a few days while fixing crbug.com/720776 . It should all be working now. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, May 25 2017Labels: Needs-Triage-M60 Needs-Bisect