WebAPI/2014-09-30
From MozillaWiki
< WebAPI
« previous week | index | next week »
WebAPI Meeting Details
- Tuesday 2014-09-30 - 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
- The path to <webview>
- Expose browser API to HTMLIFrameElement's prototype (bug 1044736)
- Make some currently privileged browser API certified only?
- we had a discussion about this and there were many questions about whether or not this is worth pursuing
- Some background on the existing B2G browser situation: https://hacks.mozilla.org/2014/08/building-the-firefox-browser-for-firefox-os/
- Kan-Ru: I recommend starting an email thread on dev-webapi about this
- current <mozbrowser> is privileged API and we want to make changes to it that will only be useful for certified apps
- Ehsan thinks it should be certified-only and that the current privileged exposure is a bug
- having <webview> avoids overloading <iframe> and provides clarity
- annevk brought up concerns around HTML parser and certified-only APIs
- Fine-grained visibility API or display a static image when setVisible(false) (bug 1034001)
- Ehsan brought up the tying of things (playing audio, screenshot, etc.) to the visibility state of the document and how desktop is different than what we do on B2G here
- Session/State restore (bug 1033999)
- low-level API + letting Gaia browser app do session restore
- FileSystem and DeviceStorage on PBackground
- ATM there is a DeviceStorage implementation of the FileSystem API which uses IPC for communication and all the work is done in an I/O thread
- baku plans to implement the FileSystem API for a sandboxed filesystem
- should the existing DeviceStorage implementation be rewritten to use PBackground?
- yes, because FileSystem will be useful on workers
- yes, because quotamanager itself will move to PBackground in the future (I think this is what Jan said)
- yes, because FileSystem uses FileHandle which will also move to PBackground
