WebAPI/2014-05-27

« previous week | index | next week »

WebAPI Meeting Details

• Tuesday 2014-05-27 - 8:00 am Pacific

• Dial-in: Audio-only conference# 98413
  • People with Mozilla phones or softphones please dial x4000 Conf# 98413
  • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 98413
  • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 98413
  • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 98413
  • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 98413
  • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 98413
  • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 98413
  • UK/London: +44 (0)207 855 3000, x4000 Conf# 98413
  • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 98413
  • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
  • SkypeOut is free if you use the 800 number
• WebAPI Vidyo Room / London-Allo Allo / Toronto-Spadina
• Join irc.mozilla.org #webapi for back channel

Notes below archived from etherpad: https://etherpad.mozilla.org/webapi-meetingnotes

Notes

• should we talk about recent intent-to-ship threads?
  • navigator.hardwareConcurrency
    • nay
  • <a ping>
    • yay!
• Marcos is implementing w3c manifest support in gecko
  • discussion has turned to role of CSP which may hold things up a bit
• Shihua helping with more porting to workers
• baku is working on a few things
  • porting some components to WebIDL
  • websocket in workers
  • blobs -> WebIDL
• janv helping with pbackground-ification (quota manager, filehandle, etc.)
• bent is leading the pbackground charge with an eye on the IDB-on-workers prize
• annevk is working on fetch spec and Fetch API integration with Service Workers
• genelian attended a TV project f2f
  • lots of feedback on TV Control API and its maturity
  • goal is a new version by end of June
• bkelly going to tackle cache implementation for service workers
  • first up: making pbackground available to workers
  • we're using pbackground for the cache objects because we want to do I/O in the parent process
  • Ehsan is concerned waiting on pbackground will delay the cache implementation
  • janv points out that quota manager will be on pbackground by the time bkelly wants to use it
  • there is just one hurdle remaining to get pbackground on workers
  • Ehsan wants to confirm with bent about waiting on