You probably just timed it right to get that behavior, bigbox for example, shrinks on hover, other themes will fade or whatever. If you are 'hovered' it will continue the animation at whatever point you were at when it goes to close the notification.
I would also add mobile webkit support, and ability to create themes with Stylus (which renders IE gradient fallbacks, easy vendor prefixing, etc). I'm not sure if the landscape has changed much but I haven't seen many that support CSS transitions. At the end of the day its just a fun experiment that some people may like and other may not :)
I had one more thought on this @danneu, I believe Growl stacks? I'm not a Mac user so I'm not sure if that is true. On Linux, Ubuntu libnotify does not, nor does Gnome Shell's notifications, two leading desktop environments for Linux and I've used both without having that desire for them to stack. Not saying stacking is not better, but I think its usable, and has its pros. E.g. how many should stack reasonably without being an issue, having a bunch stacked can crowd a portion of the screen. This lib may be able handle that in the future, but one of its strengths is that its easy for users to create vastly different themes partly because it doesn't stack. A relevant point of discussion however.
The idea of humane messages is that they require no user input to close. I do like stacking idea, maybe a future release. For now, setting the timeout to be shorter, or forcing new messages provides a workaround.
I find messages that close themselves very inhumane; I can easily miss them if I look away or switch tabs, or they can disappear while I'm trying to understand them, with no way to bring them back.
My top feature request would be a 'stays up until dismissed or navigated away from' option.
Thanks, yeah the big box apparently isn't a big hit as something more subtle like libnotify, I hope more designers come in and share their ideas, I like the jackedup that was submitted. The idea of humane message (which wasn't mine) was somewhat like the bigbox, which I liked, I think the unobtrusive part comes in that the user doesn't have to click to remove it, and getting out of the way when you want to see what's behind it. Thanks for the comment.
I failed FizzBuzz, I admit it. I was asked that as an interview question. I studied hard for my interview but I forgot about the mod operator and totally fumbled my way through the interview. I am now the Senior Web Developer and turned out to be a great asset to the company. But you wouldn't have known that from my FizzBuzz results. I also didn't have 'Computer Science' as a Major. Couple strikes. However they took a chance on me.
Since then I've been able to interview others and I look for different things than FizzBuzz compliance. I want to see how they solve problems in general. I want to see if they have any passion for what they do. I want to see things they've developed.
Thought about this too. IMO this can be handled better so many different ways by different apps and I wanted to keep the main part simple. Perhaps an add on?
Good question. I feel the notification APIs are not mature enough, plus lacking in say Firefox and IE. Plus you have more customization over notifications by not using the native API. Hopefully someday this will improve and be better supported and we can use that instead.
