Skip to content
This repository has been archived by the owner on Sep 22, 2020. It is now read-only.

Timeout doesn't work in Firefox (31) #22

Open
Noleli opened this issue Jul 30, 2014 · 6 comments
Open

Timeout doesn't work in Firefox (31) #22

Noleli opened this issue Jul 30, 2014 · 6 comments
Labels

Comments

@Noleli
Copy link

Noleli commented Jul 30, 2014

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!

@alexgibson
Copy link
Owner

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?

@alexgibson
Copy link
Owner

Perhaps it would be a good idea to set a default timeout of 4 seconds, so that all browsers are consistent?

@Noleli
Copy link
Author

Noleli commented Jul 30, 2014

Thanks for the quick reply! Yeah, a note in the docs would definitely be helpful. When it's null, it sticks around indefinitely in Chrome but disappears after 4 seconds in FF. I want it to persist longer, which is why it didn't seem like it was working at all in FF. Bummer that there's no way to do it in FF.

@alexgibson
Copy link
Owner

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!

@alexgibson
Copy link
Owner

Found an open bug discussing this behavior here, if you're interested: https://bugzilla.mozilla.org/show_bug.cgi?id=875114

@dandv
Copy link

dandv commented May 29, 2015

Ben's narrow-minded perspective in that bug is sad.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants