{"id":339,"date":"2014-10-18T22:38:42","date_gmt":"2014-10-18T22:38:42","guid":{"rendered":"http:\/\/aurelio.audero.it\/blog\/?p=339"},"modified":"2025-05-04T22:15:30","modified_gmt":"2025-05-04T22:15:30","slug":"state-web-notifications-api","status":"publish","type":"post","link":"https:\/\/www.audero.it\/blog\/2014\/10\/18\/state-web-notifications-api\/","title":{"rendered":"The State of the Web Notifications API"},"content":{"rendered":"

Today I was reviewing my HTML5 API demos<\/q><\/a> repository to keep its information updated and relevant. In the last two weeks Google has released Chrome 38<\/a>, Opera has released Opera 25, and Mozilla has released Firefox 33<\/a>. Every time a new version of a browser is available, it may introduce support for new APIs or change an already supported API to accommodate changes in the specifications. For these reasons, a general check was much needed.<\/p>\n

In this article I’ll discuss what’s the current state of the Web Notifications API, what browsers support it, and what versions of the specifications. I’ll use this post also to summarize some inconsistencies I’ve found along the way.
\n<\/p>\n

\"push<\/p>\n

Introductory notes<\/h2>\n

First of all, if you’re reading this article and you need an introduction to the Web Notifications API, I suggest you to read my article An Introduction to the Web Notifications API<\/q><\/a>.<\/p>\n

The second important point is that the Web Notifications API have two specifications: the W3C<\/abbr> specifications<\/a> and the WHATWG<\/abbr> specifications<\/a>. The last version of the W3C specifications dates back to latter is more the 12 September 2013, while the last update of the WHATWG specifications was made the 12 October 2014. The freshness of the last update isn’t the only difference and I’ll highlight some of them in the remainder of this article.<\/p>\n

Thanks to Anne van Kesteren<\/a>, now I have an even better understanding on what’s going on in regard of the Web Notifications API and the WHATWG<\/abbr> specifications, so I’ve updated this article. The main point I discovered is that only very recently the WHATWG<\/abbr> specifications have dropped the onclose<\/code> and the onshow<\/code> event.<\/ins><\/p>\n

As a final note, all the assertions I’ll made are based on my tests using the demo page<\/a> I’ve build for HTML5 API demos<\/q>.<\/p>\n

With these brief notes in mind, let’s now go back to the main topic. Please note that I will not cover Safari because I don’t (and will never) have a Mac.<\/p>\n

Chrome 38<\/h2>\n

At the moment it’s hard to say for me if Chrome implements the W3C or the WHATWG<\/abbr> specifications. My understanding is that up to Chrome 37, the browser supported the W3C<\/abbr> specifications, and starting from version 38 it supports the WHATWG specifications. However, because I’m analyzing only the last version of every browser, I’ll focus on Chrome 38 and its adherence to the WHATWG specifications. Said that, I see the following issues:<\/p>\n