The close()
method of the Notification
interface is used to close a previously displayed notification.
Syntax
Notification.close();
Parameters
None.
Returns
Void.
Examples
In the following snippet, found in our Emogotchi demo (view it running live), we have a simple function that when called creates an options
object and then a new notification. At the end of the function, it also calls close()
inside a setTimeout()
function to close the notification after 4 seconds (some browsers close spawned notifications automatically, and some such as Chrome and Opera do not.) Also note the use of bind()
to make sure the close()
call is associated with the notification.
function spawnNotification(theBody,theIcon,theTitle) { var options = { body: theBody, icon: theIcon } var n = new Notification(theTitle,options); setTimeout(n.close.bind(n), 4000); }
Specifications
Specification | Status | Comment |
---|---|---|
Notifications API | Living Standard | Living standard |
Browser compatibility
Feature | Chrome | Edge | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|---|
Basic support | 5webkit[1] 22 |
(Yes) | 4.0 (2.0)moz[2] 22.0 (22.0) |
No support | 25 | 6[3] |
Feature | Android | Android Webview | Edge | Firefox Mobile (Gecko) | Firefox OS | IE Mobile | Opera Mobile | Safari Mobile | Chrome for Android |
---|---|---|---|---|---|---|---|---|---|
Basic support | ? |
(Yes) |
(Yes) | 4.0 (4.0)moz[2] 22.0 (22.0) |
1.0.1moz[2] 1.2 |
No support | ? | No support |
(Yes) |
[1] Before Chrome 22, the support for notification followed an old prefixed version of the specification and used the navigator.webkitNotifications
object to instantiate a new notification.
Before Chrome 32, Notification.permission
was not supported.
Before Chrome 42, service worker additions were not supported.
[2] Prior to Firefox 22 (Firefox OS <1.2), the instantiation of a new notification must be done with the 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).