onnotificationclose handler is not called from the Notification center in Chrome 60 - canary
Reported by
vishalsi...@yahoo-inc.com,
May 15 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3096.0 Safari/537.36 Steps to reproduce the problem: 1. Create a push subscription from Chrome 60 on Mac via a Service worker (SW) 2. Create a `notificationclose` handler in the service worker 3. Show a notification via the SW (as a result of push message) 4. Close the notification from Mac's notification center What is the expected behavior? notificationclose should be called. What went wrong? notificationclose is not called. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 60.0.3096.0 Channel: canary OS Version: OS X 10.12.4 Flash Version:
,
May 16 2017
vishalsingh@, does this work in earlier Chrome versions? Is it a regression?
,
May 16 2017
,
May 16 2017
Mac OS X unfortunately doesn't give us accurate callbacks when the notification has been dismissed. This can happen in various cases: the user clicks on the Close button (or swipes it away) whilst the notification is on-screen -- for this you get the callback, or the user closes it (through the Close All button if you want) in the notification center -- for this you won't get the callback. What you can do is poll SWR.getNotifications() every now and then to get the insight you want. This is the same on Android by the way - we can't always accurately report a notification as closed there either, and it's likely to be the same on Windows when we start using native notifications there.
,
May 16 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by manoranj...@chromium.org
, May 15 2017