On Oct 23, 2013 8:53 AM, "Anne van Kesteren" <annevk@annevk.nl> wrote: > > On Wed, Oct 23, 2013 at 4:37 PM, Andrew Wilson <atwilson@google.com> wrote: > > Applications can also register a window.onclose method to close any pending > > notifications (gmail does this) if that's the behavior they want. > > > > I don't think this addresses issues where the window itself crashes or is > > shutdown due to memory constraints, however. It's not clear to me that we > > *should* auto-close notifications - I suspect that there are arguments in > > favor of keeping those notifications open (for example, if my calendar web > > page crashes, should I really miss out on any notifications that were > > displayed?) > > I could see an argument for having some convenience features here. > E.g. being able to define a timeout when creating a notification. > However, it seems we should wait a bit longer until there's more > deployment of this feature to find out what the actual common pain > points In general UI that automatically goes away and is no way for the user to get back to is considered bad UI. So I wouldn't be in a hurry to add this. / Jonas
Received on Wednesday, 23 October 2013 18:34:51 UTC