Trying the notification API on Android, I ran into the following:

http://stackoverflow.com/questions/29774836/failed-to-construct-notification-illegal-constructor

Not sure about iOS support. I was wondering, are there any plans to support mobile browsers through the ServiceWorkerRegistration.showNotification() API? Especially since the Notification API may be removed in future versions of desktop Chrome. It seems to me that this library would be a great place to wrap all these different APIs and try to get a solution that works on most devices.

Still quite a way to go, but the basics are here.

Things working:

• New extra options in Notify.js for Service Worker API
• Notify.js works in service workers too if permission was granted

TODO:

• Testing (suggestions would be very much appreciated)
• Update README.md
• Event handling. Apparently show and close are being deprecated, different behavior on service workers, need more investigation.
• Maybe we'll think of something else

Hey, I've updated to 2.0.2 and noticed that it exports differently. I'm using Babel + CommonJS Module Plugin. Since 2.0.2 I have to do the following:

import Notify from 'notifyjs';
if (Notify.default.needsPermission) {
  Notify.default.requestPermission();
}

Notice the default. - apparently it exports a Object that has a default member as default.

I think it's unreasonable for a package to require the user to manually install something to be able to use your package.

Your package may depend on jspm if you want but I expect all package to be installable simply with a npm install.

For instance, all my packages (see this one for instance) are transpiled to ES5 before publishing.

yeah basically "Click function won't work if browser or page is not focused" the notification is just close. Is this function needs to be simple like window.open or something ?

Our clients make heavy use of notifications and Chrome 47s removal of their notification center broke some things. This was my attempt to fix it. I thought I'd share if you'd like to use it.

This PR:

1. passes along the requiredInteraction field that Chrome respects
2. adds a field to close the notification on click when a requiredInteraction is used (bug in chrome?)
3. adds a hack to Firefox to continually call notifications when the requiredInteraction field is used until the user clicks it (ugly, but effective)

Hey guys, I am having an issue with notify.js when running unittests out of karma/PhantomJS after updating to to notify.js v1.2.6: ReferenceError: Can't find variable: Notification at /Users/beane/Code/debug-notify.js/bower_components/notify.js/notify.js:105

This error is thrown before any of my tests run. Here are my dependency versions: "devDependencies": { "bower": "1.5.3", "jasmine-core": "2.3.4", "karma": "0.13.10", "karma-jasmine": "0.3.6", "karma-phantomjs-launcher": "0.2.1", "phantomjs": "1.9.18" }

Demo here: https://github.com/ErikBean/debug-notify.js

Any help with this would be great, as our dev team is stuck with the previous version until this gets resolved. Thanks, -Erik

Added Notify.isSupported(), Notify.needsPermission(), Notify.requestPermission() so we can call these functions without having to create a new Notify object.

At least your demo page (http://alxgbsn.co.uk/notify.js/) displays notifications fine in desktop and mobile Firefox, as well as in desktop Chrome, but doesn't do anything neither in mobile Chrome, nor in Android default browser. I have tested it on:

• Highscreen Alpha GT - Android 4.0.3, Chrome 30.0.1599.82
• Digma iDxD10 - Android 4.0.4, Chrome 28.0.1500.94

(I don't know how to look up the default browser's version). Please rectify, as I'm really looking forward to using your library. I'd be happy to provide assistance, if need be.

Hi,

I have a strange behaviour with Notifications on Firefox. I use the version 45.0.1 both on Debian and Windows.

This code shows up the notification on Windows but not on Debian:

var Notify              = require("notifyjs");
var prepareNotification = function () {
    var timeoutNotification = new Notify("Inactivité détectée", {
        body: "Vous serez déconnecté pour cause d'inactivité dans 60 secondes.",
        closeOnClick: true,
        timeout: 5,
        icon: "http://domain.tld/example.png"
    });

    timeoutNotification.show();
};

if (!Notify.needsPermission) {
    prepareNotification();
} else if (Notify.needsPermission && Notify.isSupported()) {
    Notify.requestPermission(function () {
        prepareNotification();
    });
}

Your demo page works both on Windows and Debian: https://alexgibson.github.io/notify.js/

All is working fine with Chrome.

it occures when write

var myNotification = new Notify('Yo dawg!', { body: 'This is an awesome notification', notifyShow: onNotifyShow });

function onNotifyShow() { console.log('notification was shown!'); }. it will give notify not define error ("i am not using require here").

and if i use require like:

var Notify = require('notifyjs') var myNotification = new Notify('Yo dawg!', { body: 'This is an awesome notification', notifyShow: onNotifyShow });

function onNotifyShow() { console.log('notification was shown!'); }.

then it shows /Volumes/Project data/node/demo/node_modules/notifyjs/dist/notify.js:63 var N = window.Notification; ^ window is not defined. please help

This is more a heads up, but when I publish version 4.0 of this library I plan to:

• Publish as a native ES module (all evergreen browsers now support modules natively).
• Remove the transpiled version from the repo (removing both rollup and babel as dependencies).
• Remove Bower support.

If folks want the ES5 compatibility, they can still transpile using their own builds.

Knock Knock :door: anybody still here ? :smile:

I noticed an error in our logs : You must only call this before calling Notification.requestPermission(), otherwise this feature detect would trigger an actual notification! and I know why it happens.

The problem :

Imagine a scenario where a user opens up a web chat app in two different browser tab. At some point the user receives a chat message and the app ask for permission to display web notifications. Since the app is realtime, it will ask for permission in BOTH tabs at the same time. The user may then click "allow" in the current tab and leave the other untouched.

At this point, Notify.needsPermission will still be true in the other tab even if N.permission === 'granted', which will then lead us to calling Notify.isSupported() and triggering the error in the other tab when a new message is received.

The fix :

I think it's safe to assume that if the permission has been granted already, this feature MUST be supported ! Therefore we can just return true there, instead of throwing and error.

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 on start :man_shrugging:

The latest version of requestPermission deprecates the callback interface in favor of a Promise-based interface. This library should support the Promise-based interface as well.

It looks like Safari doesn't currently support the Promise interface, but it should be possible for this library to have its requestPermission both take a callback and return a promise for backwards compatibility.

I think it might be a good idea to use PageVisibility API to display notifications only when page is not visible for example, like https://github.com/ttsvetko/HTML5-Desktop-Notifications

Notify.config({
    pageVisibility: true|false
})

Firefox forces notifications to close after about 4 seconds regardless of the timeout option. It works fine in Chrome. This note may have something to do with it. Thanks!