Open
Bug 1466499
Opened 6 years ago
Updated 1 year ago
Inline replies to web notifications should be supported
Categories
(Core :: DOM: Notifications, enhancement, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: anita.woodruff, Unassigned)
References
(Blocks 2 open bugs, )
Details
(Keywords: parity-chrome)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36
Steps to reproduce:
Attempt to fire a notification which accepts an inline reply from the user typing into the notification, as per the recently proposed changes to the Notifications API:
Spec change pull request: https://github.com/whatwg/notifications/pull/132
Explainer: https://github.com/anitawoodruff/inline-notification-replies
Actual results:
Unsupported.
Expected results:
Web developers should be able to show notifications that let users type a reply within the notification, and this reply should be delivered back to the service worker in the notificationclick event.
Updated•6 years ago
|
Blocks: ServiceWorkers-compat
Updated•6 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
The spec is not there yet, and it's surprising given that Chrome has been shipping this for years. https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/notifications/notification_event.idl;l=14;drc=047c7dc4ee1ce908d7fea38ca063fa2f80f92c77
Keywords: parity-chrome
Blocks: 1844584
Type: defect → task
Type: task → enhancement
You need to log in
before you can comment on or make changes to this bug.
Description
•