On 5 August 2014 16:30, Anne van Kesteren wrote:
> On Tue, Aug 5, 2014 at 5:04 PM, Peter Beverloo
> wrote:
> > On Tue, Aug 5, 2014 at 3:48 PM, Anne van Kesteren
> wrote:
> >> Is that available within a service worker?
> >
> > It would be reasonable to expose it, but it currently isn't (afaik).
On Tue, Aug 5, 2014 at 5:04 PM, Peter Beverloo wrote:
> On Tue, Aug 5, 2014 at 3:48 PM, Anne van Kesteren wrote:
>> Is that available within a service worker?
>
> It would be reasonable to expose it, but it currently isn't (afaik).
Okay, we'd need to sort that out somehow.
> Defaulting to the
On Tue, Aug 5, 2014 at 3:48 PM, Anne van Kesteren wrote:
> On Tue, Jul 29, 2014 at 4:28 PM, Peter Beverloo
> wrote:
> > When used from a Service Worker, the attribute will implicitly default to
> > the ServiceWorkerRegistration of the running Service Worker.
>
> Is that available within a servic
On Tue, Jul 29, 2014 at 4:28 PM, Peter Beverloo wrote:
> When used from a Service Worker, the attribute will implicitly default to
> the ServiceWorkerRegistration of the running Service Worker.
Is that available within a service worker?
> If serviceWorker is set to null/undefined within a Servi
To summarize a discussion we had about this on IRC today:
http://krijnhoetmer.nl/irc-logs/whatwg/20140729#l-509
Jungkee wrote a helpful document for features using Service Workers as well:
https://gist.github.com/jungkees/3154398b8deee7c70139
The |serviceWorker| attribute can be added to
On 15 May 2014 17:13, "Peter Beverloo" wrote:
> (snip)
>
> For |notificationshow|, there is a worry here that if we decide to support
> delayed notifications, it would enable developers to use notifications to
> set precise timers: create a delayed notification to be displayed an hour
> from now,
On Fri, May 16, 2014 at 4:02 PM, Peter Beverloo wrote:
> On Fri, May 16, 2014 at 2:57 PM, Anne van Kesteren wrote:
>> Service worker integration makes sense to me. I guess I'll wait with
>> updating the Notifications API until that is further along.
>
> Do you have a specific milestone in mind?
On Fri, May 16, 2014 at 2:57 PM, Anne van Kesteren wrote:
> On Thu, May 15, 2014 at 6:12 PM, Peter Beverloo
> wrote:
> > For |notificationshow|, there is a worry here that if we decide to
> support
> > delayed notifications, it would enable developers to use notifications to
> > set precise time
On Thu, May 15, 2014 at 6:12 PM, Peter Beverloo wrote:
> For |notificationshow|, there is a worry here that if we decide to support
> delayed notifications, it would enable developers to use notifications to
> set precise timers: create a delayed notification to be displayed an hour
> from now, ge
One amendment to (3), which events to expose on the
ServiceWorkerGlobalScope, is that we should only expose the
|notificationclick| and |notificationclose| events.
The benefit of not exposing |notificationerror| is that there are two
situations in which we would fire the event: (a) when there is n
Based on Anne's Reviving Notification Objects thread from last year, I
would like to propose an alternative solution.
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-March/251058.html
There are known lifetime issues with Notifications, and rather than tying
them all to the page, how abo
11 matches
Mail list logo
