WebAPI/2013-09-24
From MozillaWiki
< WebAPI
« previous week | index | next week »
WebAPI Meeting Details
- Tuesday 2013-09-24 - 10: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 / SF-Golden Gate (3rd floor) / Toronto-Spadina
- Join irc.mozilla.org #webapi for back channel
Notes will be taken on etherpad: https://etherpad.mozilla.org/webapi-meetingnotes
Minutes
- priority of async IDB on workers vs. sync IDB on workers
- sync will require lots of Ben's time for review
- event and eventdispatcher unified implementation from smaug just landed
- Jan thinks he can have a patch ready for Ben's review by mid-October
- if he drops the current work, it'll be more work in the future due to rebases, etc.
- priority-wise, async IDB on workers is higher priority for desktop
- on B2G, sync IDB on workers can unblock gaia
- sicking thinks we need more agreement at spec level for sync before shipping it on desktop; but could turn on on nightly and aurora (not beta/release) to get feedback from authors
- Jan says we'll have IDB ported to WebIDL in ~1 week
- IPC thread for workers and child processes will also be done very soon
- API availability on a platform vs. security restrictions around that API
- Jan will work with Google and others on temporary storage syntax
- Google suggested 3 approaches and we're doing one of them; just need to get agreement
- Unimplemented Web APIs are stubbed out inappropriately
- https://bugzilla.mozilla.org/show_bug.cgi?id=859554
- use case: marketplace knowing if users can run apps which require higher privileges than marketplace app itself
- Don't expose properties of APIs when they're not supposed to be available
- https://bugzilla.mozilla.org/show_bug.cgi?id=838614
- Summit demos
- we decided we'd do a 30 minute open session of WebAPI Q&A instead ... no one will be in Santa Clara to do it but that's okay
