On Android, replying to a notification displays a spinner until the notification is dismissed/updated |
|||
Issue descriptionIf the site doesn't handle the reply by closing the notification or updating it manually, a spinner is shown once the user presses reply which continues spinning even after the reply has been delivered to the service worker in the notificationclick event. Not sure if this is a 'WontFix' because sites should handle this, or whether we should do what Android recommends and update the notification with the reply, as recommended at https://developer.android.com/training/notify-user/build-notification#retrieve-user-reply Seems like a platform-specific footgun so I'm tempted to say the latter. What do others think?
,
Jun 1 2018
Another option is just to update the notification but not include any new data, which will at least get rid of the spinner, after the notification click promise has been resolved.
,
Jun 4 2018
,
Jun 6 2018
Discussed this with peter@ yesterday and we concluded that it should be the web developer's responsibility to close or update the notification upon receiving a reply, on all platforms. |
|||
►
Sign in to add a comment |
|||
Comment 1 by peter@chromium.org
, Jun 1 2018