That HAS to violate some sort of User Experience. If it doesn't I am going to say it violates mine.
Also, I noticed that only one notification is visible at a time. It would be nice to be able to chain notifications to have more than just one visible notification.
Out of 12 comments on here, 2 are already about disliking the initial "big text box" example.
They should make lib notify the first one, and try to get some additional themes that showcase it. The 3 that are there are pretty simple and two are big annoying textboxes.
Also, the notifications behave strange when hovering over them with the mouse... they shrink onhover, then on the next hover they dismiss.
This is on Chromium 15.
My experience with websites that queue up notifications (the old thesixtyone.com) is that you sort of pause, sit there, and wait for them to finish up so you see what they say. A better experience is for them to stack up in the corner so you can read them, then click them away once you're done.
My top feature request would be a 'stays up until dismissed or navigated away from' option.
Not saying this or any other implementation is bad and you shouldn't use it, but why does hacker news get so excited every time one of these shows up?
I'm looking for some 'arguments' to seriously consider something like this - Thank you ;-)
Otherwise it seems similar to most of the others.
Design wise, the default is pretty obtrusive.
Nice library though. Thanks.
