- From: Robert Bîndar <robertbindar@gmail.com>
- Date: Mon, 29 Sep 2014 12:54:48 +0300
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: WHATWG <whatwg@whatwg.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Jake Archibald <jaffathecake@gmail.com>, Andrew Wilson <atwilson@google.com>, Peter Beverloo <beverloo@google.com>
Sounds exactly like an use case of the 'data' attribute. 2014-09-29 12:23 GMT+03:00 Jonas Sicking <jonas@sicking.cc>: > On Sun, Sep 28, 2014 at 11:15 PM, Andrew Wilson <atwilson@google.com> > wrote: > >> * Dropping the close event. > >> > >> I've been wondering myself whether it's valuable to support this. Like > >> Tab, I'm not aware of any messaging application actually using the close > >> event as an indication that the message has been read. There is the > "dismiss > >> all" button on most platforms, which definitely does not imply having > read > >> the message. It's actually an interesting privacy question as well, for > >> example, if a user dismisses a Facebook notification in their > notification > >> center without actually starting the app, should the sender be informed > >> about them having at least looked at their phone? > > > > Gmail tracks information internally about all open notifications so it > knows > > what chat window, email, etc to display when the user clicks on one. It > > cleans up those data structures as notifications are closed, so if we > stop > > generating close events, then gmail will leak even more memory than it > > currently does :) > > Could this be solved by using the 'data' attribute when creating a > Notification? > > / Jonas >
Received on Monday, 29 September 2014 09:55:16 UTC