-
Notifications
You must be signed in to change notification settings - Fork 29
Description
Description
The Notifications API allows web pages to control the display of system notifications to the end user. These are outside the top-level browsing context viewport, so therefore can be displayed even when the user has switched tabs or moved to a different app. The API is designed to be compatible with existing notification systems, across different platforms.
MDN - Notification API
While all major browser engines now support the Notification API (and related API's like Web Push, etcetera), there remain a lot of unsupported features, experimental features that I would love to see moving forward, and most importantly bugs that make the Notification API unreliable.
I think that it goes without saying that the ability to send push notifications is very important. If the Notification API is incomplete and/or unreliable, many businesses will opt to build native apps instead.
Note: Also proposed for Interop 2025 (#737)
Specification
https://notifications.spec.whatwg.org/
web-feature
No response
Test Links
https://wpt.fyi/results/notifications
Additional Signals
Browser bug reports
The list below is probably far from complete, but it gives a good idea:
Chromium
- renotify=true does not work on macOS
- macOS 15 - WebPush - "This site has been updated in the background" even when rules are followed
- SW: push messages not waking Android 8.0 from deep sleep
WebKit
- notificationclick events in serviceworkers not firing
- Clients.openWindow resolving promise too early
- notificationclose event not firing when notification cleared
- Push notifications with same tag do not replace each other
- Notifications API: support for the
badge
option - Notifications API: support for the
icon
option
Usage:
https://chromestatus.com/metrics/feature/timeline/popularity/371
Metadata
Metadata
Assignees
Labels
Type
Projects
Status