-
Notifications
You must be signed in to change notification settings - Fork 146
Timeout doesn't work in Firefox (31) #22
Comments
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 a notification automatically after 4 seconds. So if your timeout value is longer than 4 seconds, it does nothing. There is no way to override browser behavior, so other than add a note in the docs (which is definitely worth doing), I'm not sure what else would be expected? |
Perhaps it would be a good idea to set a default timeout of 4 seconds, so that all browsers are consistent? |
Thanks for the quick reply! Yeah, a note in the docs would definitely be helpful. When it's |
Yeah, I can't see anything in the spec that mentions notifications should close after 4 seconds. But if this is the behavior both Firefox and Safari have adopted, maybe we should make Chrome follow suit for now. I'll leave this open and updates the docs (as well as set a new default timeout value). Thanks! |
Found an open bug discussing this behavior here, if you're interested: https://bugzilla.mozilla.org/show_bug.cgi?id=875114 |
Ben's narrow-minded perspective in that bug is sad. |
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!The text was updated successfully, but these errors were encountered: