Issue metadata
Sign in to add a comment
|
Chrome doesn't open page when clicking on notification sent via Push API on Android
Reported by
teodorma...@gmail.com,
Apr 1 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: Website registers a service worker, requests and receives the permissions for Push API and Notifications API to function. A notification is sent via Push API to client. The notification is handled by the service worker and displayed on the device. Person taps on the notifications in the notifications center. What is the expected behavior? Service worker's notificationclick event handler is triggered, which in turn calls self.clients.openWindow(URL) to open the desired page. What went wrong? A "Complete action using" dialog is open, with no option for completing the action in Chrome (or any other browser). None of the provided options produce meaningful results. All apps just open the default activity. I've attached a portion of syslog filtered by 'chromium'. There is also a simplified version of the service worker provided. Did this work before? Yes Chrome version: 56.0.2924.87 Channel: stable OS Version: 4.2.1 Flash Version:
,
Oct 30 2017
Unfortunately, I no longer have access to that version of Android. It works correctly on Android 5.1 in Latest Stable. I think we can close this issue now, as nobody else seems to have been affected.
,
Oct 30 2017
Thank you for providing more feedback. Adding requester "msrchandra@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
,
Nov 1 2017
Closing this issue as per comment #2 Thanks!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Oct 30 2017Labels: Needs-triage-Mobile Needs-Feedback