- From: Laurent Perez <l.laurent.p@gmail.com>
- Date: Thu, 8 May 2014 20:21:23 +0200
- To: Marcos <marcos@marcosc.com>
- Cc: "public-web-mobile@w3c.org" <public-web-mobile@w3c.org>, Tobie Langel <tobie.langel@gmail.com>
Hi I too think getting usable builds is a blocker for ServiceWorker. I'm interested by one or two demos, I've tried a very basic prototype on chrome canary 36.0.1981.3, unfortunately "install" or "fetch" events do not fire at all so it's unusable. The spec built from github mentions "onchange" and "onfetch" but they do not fire either. navigator.(moz)serviceWorker is undefined in firefox aurora. I understand work is in the early stages, after seeing https://code.google.com/p/chromium/issues/list?q=label:Cr-Blink-ServiceWorker laurent On Thu, May 8, 2014 at 7:23 PM, Marcos <marcos@marcosc.com> wrote: > > > > On May 8, 2014 at 7:23:16 AM, Maffett, Ian (ian.maffett@intel.com) wrote: >> > Once I have access, I¹ll start playing around with the repo¹s >> and touch base again. > > Note that the work for the repos I added you too are just starting up (except "installable-apps", which a few of us have been hacking on for a while). > > About orientation, we are still trying to get organized. I'm hoping Lars (cc'ed) will take the lead on how we should proceed. We probably need to set up a call just to work out who wants to do what, and how much time people can contribute. > > About service workers, I'm hopeful Tobie (cc'ed) will lead there. Tobie, what do you think? I think the biggest blocker is getting usable builds from browser vendors right now. > -- http://laurentperez.fr J2EE tips and best practices
Received on Thursday, 8 May 2014 18:23:03 UTC