{{APIRef("Web Notifications")}}
The Notification
interface of the Notifications API is used to configure and display desktop notifications to the user.
{{AvailableInWorkers}}
Constructor
- {{domxref("Notification.Notification", "Notification()")}}
- Creates a new instance of the
Notification
object.
Properties
Static properties
These properties are available only on the Notification
object itself.
- {{domxref("Notification.permission")}} {{readonlyinline}}
- A string representing the current permission to display notifications. Possible value are:
denied
(the user refuses to have notifications displayed),granted
(the user accepts having notifications displayed), ordefault
(the user choice is unknown and therefore the browser will act as if the value were denied).
Instance properties
These properties are available only on instances of the Notification
object.
- {{domxref("Notification.title")}} {{readonlyinline}}
- The title of the notification as specified in the options parameter of the constructor.
- {{domxref("Notification.dir")}} {{readonlyinline}}
- The text direction of the notification as specified in the options parameter of the constructor.
- {{domxref("Notification.lang")}} {{readonlyinline}}
- The language code of the notification as specified in the options parameter of the constructor.
- {{domxref("Notification.body")}} {{readonlyinline}}
- The body string of the notification as specified in the options parameter of the constructor.
- {{domxref("Notification.tag")}} {{readonlyinline}}
- The ID of the notification (if any) as specified in the options parameter of the constructor.
- {{domxref("Notification.icon")}} {{readonlyinline}}
- The URL of the image used as an icon of the notification as specified in the options parameter of the constructor.
- {{domxref("Notification.data")}} {{readonlyinline}}
- Returns a structured clone of the notification’s data.
- {{domxref("Notification.requireInteraction")}} {{readonlyinline}}
- A {{jsxref("Boolean")}} indicating that on devices with sufficiently large screens, a notification should remain active until the user clicks or dismisses it.
- {{domxref("Notification.silent")}} {{readonlyinline}}
- Specifies whether the notification should be silent, i.e. no sounds or vibrations should be issued, regardless of the device settings.
- {{domxref("Notification.timestamp")}} {{readonlyinline}}
- Specifies the time at which a notification is created or applicable (past, present, or future).
- {{domxref("Notification.vibrate")}} {{readonlyinline}}
- Specifies a vibration pattern for devices with vibration hardware to emit.
Unsupported properties
The following properties are listed in the most up-to-date spec, but are not supported in any browsers yet. It is advisable to keep checking back regularly to see if the status of these has updated, and let us know if you find any out of date information.
- {{domxref("Notification.noscreen")}} {{readonlyinline}}
- Specifies whether the notification firing should enable the device's screen or not.
- {{domxref("Notification.renotify")}} {{readonlyinline}}
- Specifies whether the user should be notified after a new notification replaces an old one.
- {{domxref("Notification.sound")}} {{readonlyinline}}
- Specifies a sound resource to play when the notification fires, in place of the default system notification sound.
- {{domxref("Notification.sticky")}} {{readonlyinline}}
- Specifies whether the notification should be 'sticky', i.e. not easily clearable by the user.
Event handlers
- {{domxref("Notification.onclick")}}
- A handler for the {{event("click")}} event. It is triggered each time the user clicks on the notification.
- {{domxref("Notification.onerror")}}
- A handler for the {{event("error")}} event. It is triggered each time the notification encounters an error.
Obsolete handlers
The following event handlers are still supported as listed in the {{anch("browser compatibility")}} section below, but are no longer listed in the current spec. It is safe therefore to assume they are obsolete, and may stop working in future browser versions.
- {{domxref("Notification.onclose")}}
- A handler for the {{event("close")}} event. It is triggered when the user closes the notification.
- {{domxref("Notification.onshow")}}
- A handler for the {{event("show")}} event. It is triggered when the notification is displayed.
Methods
Static methods
These methods are available only on the Notification
object itself.
- {{domxref("Notification.requestPermission()")}}
- Requests permission from the user to display notifications.
Instance methods
These properties are available only on an instance of the Notification
object or through its prototype
. The Notification
object also inherits from the {{domxref("EventTarget")}} interface.
- {{domxref("Notification.close()")}}
- Programmatically closes a notification.
Example
Assume this basic HTML:
<button onclick="notifyMe()">Notify me!</button>
It's possible to send a notification as follows — here we present a fairly verbose and complete set of code you could use if you wanted to first check whether notifications are supported, then check if permission has been granted for the current origin to send notifications, then request permission if required, before then sending a notification.
function notifyMe() { // Let's check if the browser supports notifications if (!("Notification" in window)) { alert("This browser does not support desktop notification"); } // Let's check whether notification permissions have already been granted else if (Notification.permission === "granted") { // If it's okay let's create a notification var notification = new Notification("Hi there!"); } // Otherwise, we need to ask the user for permission else if (Notification.permission !== 'denied') { Notification.requestPermission(function (permission) { // If the user accepts, let's create a notification if (permission === "granted") { var notification = new Notification("Hi there!"); } }); } // At last, if the user has denied notifications, and you // want to be respectful there is no need to bother them any more. }
{{EmbedLiveSample('Example', '100%', 30)}}
In many cases, you don't need to be this verbose. For example, in our Emogotchi demo (see source code), we simply run {{domxref("Notification.requestPermission")}} regardless to make sure we can get permission to send notifications (this uses the newer promise-based method syntax):
Notification.requestPermission().then(function(result) { console.log(result); });
Then we run a simple spawnNotification()
function when we want to fire a notification — this is passed arguments to specify the body, icon and title we want, then it creates the necessary options
object and fires the notification using the {{domxref("Notification.Notification","Notification()")}} constructor.
function spawnNotification(theBody,theIcon,theTitle) { var options = { body: theBody, icon: theIcon } var n = new Notification(theTitle,options); }
Specifications
Specification | Status | Comment |
---|---|---|
{{SpecName('Web Notifications')}} | {{Spec2('Web Notifications')}} | Living standard |
Browser compatibility
{{CompatibilityTable}}
Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|
Basic support | 5{{property_prefix("webkit")}}[1] 22 |
4.0 {{property_prefix("moz")}}[2] 22 |
{{CompatNo}} | 25 | 6[3] |
icon |
5{{property_prefix("webkit")}}[1] 22 |
4.0 {{property_prefix("moz")}}[2] 22 |
{{CompatNo}} | 25 | {{CompatNo}} |
Available in workers | {{CompatVersionUnknown}} | {{CompatGeckoDesktop("41.0")}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} |
silent |
{{CompatChrome(43.0)}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
noscreen , sticky |
{{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
sound |
{{CompatVersionUnknown}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
renotify |
{{CompatChrome(50.0)}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
Promise-based Notification.requestPermission() |
{{CompatUnknown}} | {{CompatGeckoDesktop("47.0")}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} |
vibrate |
{{CompatChrome(53.0)}} | {{CompatOpera(40)}} |
Feature | Android | Android Webview | Firefox Mobile (Gecko) | Firefox OS | IE Mobile | Opera Mobile | Safari Mobile | Chrome for Android |
---|---|---|---|---|---|---|---|---|
Basic support | {{CompatUnknown}} |
{{CompatVersionUnknown}} |
4.0{{property_prefix("moz")}}[2] 22 |
1.0.1{{property_prefix("moz")}}[2] 1.2 |
{{CompatNo}} | {{CompatUnknown}} | {{CompatNo}} |
{{CompatVersionUnknown}} |
icon |
{{CompatUnknown}} | {{CompatVersionUnknown}} | 4.0{{property_prefix("moz")}}[2] 22 |
1.0.1{{property_prefix("moz")}}[2] 1.2 |
{{CompatNo}} | {{CompatUnknown}} | {{CompatNo}} | {{CompatVersionUnknown}} |
Available in workers | {{CompatUnknown}} | {{CompatVersionUnknown}} | {{CompatGeckoMobile("41.0")}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatVersionUnknown}} |
silent |
{{CompatNo}} | {{CompatChrome(43.0)}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatChrome(43.0)}} |
noscreen , sticky |
{{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
sound |
{{CompatNo}} | {{CompatVersionUnknown}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatVersionUnknown}} |
renotify |
{{CompatNo}} | {{CompatChrome(50.0)}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} | {{CompatNo}} |
Promise-based Notification.requestPermission() |
{{CompatUnknown}} | {{CompatUnknown}} | {{CompatGeckoMobile("47.0")}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} | {{CompatUnknown}} |
vibrate | {{CompatNo}} | {{CompatChrome(53.0)}} | {{CompatOperaMobile(40)}} | {{CompatChrome(53.0)}} |
[1] Before Chrome 22, the support for notification followed an old prefixed version of the specification and used the {{domxref("window.navigator.webkitNotifications","navigator.webkitNotifications")}} object to instantiate a new notification.
Before Chrome 32, {{domxref("Notification.permission")}} was not supported.
Before Chrome 42, service worker additions were not supported.
Starting in Chrome 49, notifications do not work in incognito mode.
[2] Prior to Firefox 22 (Firefox OS <1.2), the instantiation of a new notification must be done with the {{domxref("window.navigator.mozNotification", "navigator.mozNotification")}} object through its createNotification
method.
Prior to Firefox 22 (Firefox OS <1.2), the Notification was displayed when calling the show
method and supported only the click
and close
events.
Nick Desaulniers wrote a Notification shim to cover both newer and older implementations.
One particular Firefox OS issue is that you can pass a path to an icon to use in the notification, but if the app is packaged you cannot use a relative path like /my_icon.png
. You also can't use window.location.origin + "/my_icon.png"
because window.location.origin
is null in packaged apps. The manifest origin field fixes this, but it is only available in Firefox OS 1.1+. A potential solution for supporting Firefox OS <1.1 is to pass an absolute URL to an externally hosted version of the icon. This is less than ideal as the notification is displayed immediately without the icon, then the icon is fetched, but it works on all versions of Firefox OS.
When using notifications in a Firefox OS app, be sure to add the desktop-notification
permission in your manifest file. Notifications can be used at any permission level, hosted or above: "permissions": { "desktop-notification": {} }
[3] Safari started to support notification with Safari 6, but only on Mac OSX 10.8+ (Mountain Lion).