On Thu, Sep 25, 2014 at 2:28 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Sep 24, 2014 at 4:28 AM, Anne van Kesteren ann...@annevk.nl wrote:
Strawman: We classify existing notifications as non-persistent
notifications. Only notifications associated with a service worker are
persistent.
On 24 September 2014 01:21, Jonas Sicking jo...@sicking.cc wrote:
* Notifications that close when a page goes away does not seem useful
on mobile, but could be useful on desktop to enable minimized
applications, or applications whose window is covered by other
windows, call attention to
On Thu, Sep 25, 2014 at 12:25 PM, Jake Archibald jaffathec...@gmail.com wrote:
Totally agree, I didn't realise this was possible in the original proposal.
The option that makes it a persistent notification should retarget all
events to the serviceworker. If the serviceworker is invalid, I guess
On Thu, Sep 25, 2014 at 3:02 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Sep 25, 2014 at 2:28 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Sep 24, 2014 at 4:28 AM, Anne van Kesteren ann...@annevk.nl wrote:
Strawman: We classify existing notifications as non-persistent
On Thu, Sep 25, 2014 at 3:25 AM, Jake Archibald jaffathec...@gmail.com wrote:
On 24 September 2014 01:21, Jonas Sicking jo...@sicking.cc wrote:
* Notifications that close when a page goes away does not seem useful
on mobile, but could be useful on desktop to enable minimized
applications, or
On Thu, Sep 25, 2014 at 4:24 PM, Jonas Sicking jo...@sicking.cc wrote:
* Alternatively, maybe we could simply get rid of the close event
entirely. Does it have a use-case?
Yeah:
* User gets new chat message
* Push message
* Notification
* User reads chat message but doesn't need to
On Thu, Sep 25, 2014 at 4:42 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
The one example I can think of that's kinda like this is the Google
Maps Navigation Notification. It actively resists being closed, for
one thing, but it does have a Dismiss button on itself (because it's a
Rich
