DevTools/2011-08-25

From MozillaWiki
Jump to: navigation, search

Meeting Details

  • Thursday Aug 25, 2011 - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
  • 650-903-0800 or 650-215-1282 x92 Conf# 99459
  • 1-800-707-2533 (pin 369) Conf# 99459 (US)
  • #devtools on irc.mozilla.org for backchannel

Notices

  • Firebug update
    • Firebug 1.8.1 on AMO (compatible with Firefox 6)
    • Firebug 1.9a1 released tomorrow (compatible with Firefox Nightlies)
    • Firebug 1.8.2 released next week (compatible with Firefox 7)
    • Meeting notes from this week.
    • Bug 666713 - Dynamic analysis of chrome->content operations in Firefox, logging is working but there is too many logs. Waiting for a patch that allows redirecting to JS.
  • Command Line update
    • Javascript evaluation within the command line almost done.
    • More stuff will be reviewable this week.
    • Code should start landing next week.
    • i18n is largely done.
  • Highlighter update
    • Progress moving the html panel and stuf
    • A lot of stuff is really close to landing.
    • Panel docking coming soon
  • Style Inspector
    • The main style inspector bug has now passed review (woo)
    • Working on speeding up the display of properties so that it can be used with the highlighter
  • Style Editor
    • Fighting orion in the testsuite.
    • Considering some improvements for orion
    • Tests are all succeeding with orion now.
    • A number of small improvements.
    • Patch should be up this week.
  • SourceMap
    • Security review wednesday
    • Webconsole work blocked on jsdbg2 stuff
    • Hacking coffeescript to generate sourcemaps.
  • Web Console update
    • Console storage stuff is close to landing.
  • Script Debugger
    • No update.

Roundtable

  • [dchan] Security reviews
    • Talk with product/engineering to review features before they launch.
    • Curtis will be sending mail scheduling security reviews.
    • Sourcemap was reviewed yesterday.
    • Mostly concerned about content-accessible API.
    • Chrome APIs are less of a concern since websites/remote endpoints should not be able to access them
    • C/C++ rewrites of certain features are potential concerns as well, e.g. if SourceMap encoding/parsing was to be ported from JS to C/C++
  • All Hands