How to close notification after reply?

[beverloo]

How to close notification after reply?

[FluorescentHallucinogen]

Just found that if notificationclick event listener has event.notification.close() inside, then on some Android devices the notification successfully closes after clicking on "Send" icon, but on some not, the typed text is just added at the top.

This is exactly the same as the behavior of native Android apps on these devices. I've tested in Telegram. On some Android devices the notification successfully closes after clicking on "Send" icon, but on some not, the typed text is just added at the top.

But if notificationclick event listener has no event.notification.close() inside, then after clicking on "Send" icon it becomes a spinner that spins endlessly, the notification won't close on all Android devices.

@beverloo I think this is a bug, the spinner shouldn't spin endlessly, the notification should close (after some timeout). Could you please confirm?

[FluorescentHallucinogen]

Just found a very similar problem on StackOverflow: https://stackoverflow.com/q/51815139.

[beverloo]

That certainly sounds like an issue on certain builds of Android—this is one of Chrome's manual test cases iirc. The intended behaviour in the spec (& in Chrome's implementation) is that calling notification.close() always closes the notification.

[FluorescentHallucinogen]

@beverloo Could you please try to reproduce it yourself on your Android devices and your https://tests.peter.sh/notification-generator/ test page? But just remember, we are talking only about the notification inline reply case.

As I said, there are 2 problems:

1. If there is event.notification.close(), the"Send" icon becomes a spinner that spins endlessly, and the notification won't close.
2. If there is no event.notification.close(), the typed text is just added at the top, and the notification won't close.

[FluorescentHallucinogen]

@beverloo I've opened https://crbug.com/1290426.