From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

WebAPI Meeting Details

  • Tuesday 2013-07-02 - 10:00 am Pacific
  • Dial-in: conference# 98413
    • People with Mozilla phones or softphones please dial x92 Conf# 98413
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98413 (max 48 users at any time)
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 98413
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 98413
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98413
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 98413
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 98413
    • UK/London: +44 (0)207 855 3000, x92 Conf# 98413
    • FR/Paris: +33 1 84 88 37 37, x92 Conf# 98413
    • sip:conf98413@mozilla.com or, for some clients, sip:conf98413@anonsip.scl3.mozilla.com (may not work for all rooms)
    • 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


  • doc tech reviews still needed
  • people are invited to docs sprint at end of July
  • API (un)prefixing policies (Tantek bringing this up, but everyone feel free to add thoughts/URLs to this)
    • what are we doing with new(ish) APIs that we ship (no prefixes right?)
      • right, no prefixes
    • what are we doing with legacy APIs that are prefixed (any left? which? bug#s?)
      • e.g. https://developer.mozilla.org/en-US/docs/Web/API/window.requestAnimationFrame
        • requestAnimationFrame has been unprefixed.
          • so it looks like we have a docs update bug then, as the syntax examples show prefixed-only call for Firefox
      • e.g. https://developer.mozilla.org/en-US/docs/Web/API/window.mozAnimationStartTime
      • when do we unprefix them?
        • as soon as we have an unprefixed version and the web doesn't depend on the prefixed version too much (to be evaluated on a per case basis)
          • "as soon as we have an unprefixed version" sounds like a tautology - do you mean as soon as we have a spec defined for an unprefixed version?
            • Yes, having a spec is part of the process of unprefixing an API. Making sure that our implementation adheres to it is another.
          • why does "the web doesn't depend on the prefixed version too much" matter for this? wouldn't we just support both for a while? (next question handles dropping prefixes)
          • Sure, I thought you're asking about unprefixing in general.
      • when do we drop support for the prefixed versions? case-by-case? general timeout?
        • case by case, mostly
    • Great. I'd like to draft some of our WebAPI (un)prefixing policies on wikimo - I think I have enough from this Etherpad to start a stub but wanted to check with folks here to see if there were differing opinions before I did so. - Tantek
  • new work week topic: navigator.languages