It's dismissible, try showCloseButton.
It's an alternative to alert in the sense that you can use it to provide a better experience than {error: alert}. It's not a great option for modal alerts.
What browser does it not work on? We'll file an issue.
It's an alternative to alert in the sense that you can use it to provide a better experience than {error: alert}. It's not a great option for modal alerts.
What browser does it not work on? We'll file an issue.
Though they're often known as merely "notifications", that's how Growl calls them and libnotify... well no need to spell it out.
I've wanted a "just wait a minute, Javascript engine; let me look at what you're doing!" API call for quite a while.
Turns out there is one: you can put "debugger;" in any JS code, and (if you have Webkit Devtools or Firebug or what-have-you) it will act as if you had set a breakpoint right at that statement.
Much less diddling with the mouse to set a breakpoint in code you already had open in a text editor. Good complement to console.log :)
What bank do you use?
It definitely makes sense to hide the dismissal button when there are interactions prompted that would get rid of it (Retry/Cancel), but the default case is a plain text message to the user.
By the way, I like it, thanks for putting it out there! A more unique name might help me find it for future projects :)
I also had a general problem with boxes disappearing. I tried opening a box with autohide after 10 seconds, then a box with a button. I positioned my mouse over the button but then the autohide box disappeared and the button moved away from my mouse! I seriously hate such UIs. Stuff should not move on a page, especially not if they are meant to be clicked. And text boxes should not disappear when I am half-way through reading them.