notification timer
Reported by
sanja1...@gmail.com,
May 29 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1.add a feature that allow us to set a notification display time. What is the expected behavior? What went wrong? it's too frustrating when a notification arrive and do not fade out until we manually remove it. Did this work before? N/A Chrome version: 66.0.3359.181 Channel: stable OS Version: 10.0 Flash Version:
,
May 29 2018
,
May 30 2018
Thanks for filing the issue! It is understood that the issue seems to be Feature request, hence marking it as Untriaged. Requesting someone from "UI>Notifications/Blink>PushAPI" team(s) to have a look into this.
,
Jun 4 2018
Hi Sanja, Actually notifications that site sends via Chrome do generally disappear automatically after a number of seconds (the exact time depends on which operating system you are using). However, websites can choose to opt out of this behaviour by setting an option on the notification: requireInteraction to true. See this demo site for an example: https://tests.peter.sh/notification-generator/ (tick & untick the 'requireInteraction' button). If you notice notifications staying on screen indefinitely when 'requireInteraction' is *NOT* ticked, please let us know. Closing this bug as 'WontFix' because I don't think Chrome is at fault here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by e...@chromium.org
, May 29 2018Labels: -Type-Bug Type-Feature