Alex Gibson

Web Notifications aren't supported in Chrome on Android I believe, and must instead be used from within the Service Worker API. Trying `new Notification('hello');` in the browser gives the error:...

Thanks for filing this, I'll try and see to adding it soon.

This seems like a simple code change at first, but the error in place is related to the following issue https://developers.google.com/web/updates/2015/05/Notifying-you-of-notificiation-changes#android_notifications (which can also be found via the link in...

> In fact, to completely fix this scenario we would need to refactor Notify.needsPermission into a method/getter that checks if N.permission === 'granted' equals true instead of a boolean initialized...

> I almost had to add a check for IE

The next time I publish a release of this library it's going to have some substantial breaking changes anyway, so feel free...

Hi, thanks for the info Can you elaborate on what you think the behavior should be here? The timeout does work in Firefox, it is just that the browser closes...

Perhaps it would be a good idea to set a default timeout of 4 seconds, so that all browsers are consistent?

Yeah, I can't see anything in [the spec](http://www.w3.org/TR/notifications/) that mentions notifications should close after 4 seconds. But if this is the behavior both Firefox and Safari have adopted, maybe we...

Found an open bug discussing this behavior here, if you're interested: https://bugzilla.mozilla.org/show_bug.cgi?id=875114