The Web Notifications API is defined as an API for end-user notifications. A notification allows alerting the user outside the context of a web page of an occurrence, such as the delivery of email.
Thinking of some use cases for such an API isn’t very hard. For example, you may want to receive a notification as soon as you receive an email. You may also want to be notified if someone mentions you in a Tweet, or posts a photo of you on Facebook or Google+.
Now that we know what this API is, and what it’s good for, let’s delve into the description of its methods, properties, and events.
The Web Notifications API is exposed through the notification property of the window object. This is a constructor that allows us to create a notification instance. It accepts two parameters, a string containing the title of the notification, and an optional object of settings.
1 2 3 4 5 6
body: A string used to further specify the purpose of the notification.
lang: Specifies the language of the notification. Its value must be compliant with the BCP 47 standard. Examples of valid strings are en-US and it-IT.
dir: Defines the direction of the message’s text. Its value can be auto meaning that the direction is based on the browser’s settings, ltr to specify a left-to-right direction (for European languages), or rtl to specify a right-to-left direction (for some Asian languages).
tag: A string that is used as an ID that can be employed to retrieve, replace, or remove the notification.
icon: Specifies the URL of an image that will be used as the notification’s icon.
Sometimes we may need to perform an action as soon as the status of the notification changes. For example, we may want to know if the user has clicked the notification, or when it is closed. To do that, we can attach a handler to one of the four events exposed:
onclick: Fired when the user clicks on the notification.
onclose: Fired as soon as the user or the brower closes the notification.
onerror: Fired if an error occurs with the notification.
onshow: Fired when the notification is shown.
1 2 3 4 5 6 7
Before you display a notification you need to ask the user for permission.
1 2 3
Once the user grants you permission you are good to go. At any point you can check the granted permission using Notifcation.permission property. It can have one of the following values :
granted: The user has granted the permission.
denied: The user has denied the permission.
default: The status is unknown. The browser will treat this as if the user denied the permission.
Support for the Web Notifications API isn’t very good on both desktop and mobile. On desktop, Chrome and Firefox implemented the first version of this API a while ago. However, considering only the new version of the API, implementation starts from Chrome 22 and Firefox 22 (both without a vendor prefix). Safari 6+ also supports the Web Notifications API. On the mobile side of things, only Firefox and Blackberry have full support. Testing if a browser supports this API is a matter of writing a check like the one shown below:
1 2 3 4 5
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
So far so good, That’s it!!! See ya!!! :)