DevTools/2011-04/28
From MozillaWiki
< DevTools
Meeting Details
Due to problems with our usual conference bridge, this week we will be using conference number 364 (rather than the usual 9364).
- Thursday Apr. 28, 2010 - 8:00am Pacific, 11:00am Eastern, 15:00 UTC
- 650-903-0800 or 650-215-1282 x92 Conf# 364
- 1-800-707-2533 (pin 369) Conf# 364 (US)
- #devtools on irc.mozilla.org for backchannel
Notices
- Welcome Panagiotis Astithas
- past on github, irc, bugzilla
- Firebug update
- working on Firebug 1.7. 1.7.1b2 tomorrow, final version in 1-2 weeks
- concentrating on 1.8
- continuing module work (converting all files to RequireJS AMD modules)
- this can help with Firefox startup time
- want to get rid of XUL overlays. this will help make Firebug restartless.
- remote debugging via Crossfire
- Plan is to ship Firebug 1.8 concurrent with Firefox 5 (June 22nd)
- Web Console update
- Web Console test plan from QA: https://wiki.mozilla.org/QA/Waverley/Developer-Tools/Web-Console/Test-plan
- Workspaces update
- New name: Scratchpad
- Testplan https://wiki.mozilla.org/QA/Waverley/Developer-Tools/Workspaces/TestPlan
- Adding a Web Developer submenu to the Tools menu
- Scratchpad, Web Console, Error Console and Inspector menu options will move there
- QA found a couple of bugs to fix
- Highlighter update
- Fixing up unit tests that were broken by changing
- msucan helped with that. There's now about 3 left
- there are a couple of panel timing sorts of issues
- Command Line update
- there is an hg repository that allows you to register commands, type commands in the web console, etc.
- jwalker will keep this up to date with the devtools repo
- needs a toggle to switch between JS and command mode
- needs to be able to hide behind a pref, which should be straightforward
- CSS Inspector
- Removed the stylesheet selector and is going to remove specificity which will both clean things up a bit
- View source
- Talking with Henri Sivonen about the HTML5 parser-based reimplementation. That is largely the toolkit version of View Source
- msucan has been working on integrating Ace with browser chrome. getting things packaged up in .jsm's.
- starting up work on view source UI
- the pilot.jsm from GCLI work was useful
- CSS Editing
- editor needs a stylesheet selector still. currently it's a menu popup.
- experimented with a listbox so that you can have the list of stylesheets in a sidebar
- Still having trouble with the gzipped cache data coming up encoded rather than in usable source form
- Henri Sivonen recommends looking at the new view source code bug 482921
- HTML tree
- jviereck stepped up with code folding implementation for Ace, which we will want to make use of at some point
- for now, going with more traditional tree view
- going to try to implement structured editing in the HTML tree, but hopefully less annoying
- want to make it so that you can edit the entire list of attributes with a single text box, rather than having to do each attribute independently
- also need to add text node editing
- Debugger
- we have breakpoints now and embryonic support for stopping at breakpoints and resuming
- thinking about reworking UI a bit
- likes how Chrome serves up the debugger directly when you start the remote debugging server
- by next week we should have stop/resume/step with current stack shown
- currently looking at Chrome's remote debugger protocol as an alternative to jblandy's
- jblandy's protocol is nicer, but no showstoppers in Chrome's protocol yet
- protocol is here: http://code.google.com/chrome/devtools/docs/remote-debugging.html
Roundtable
- Sandboxes
- instanceof isn't working as expected in a sandbox
- looks like a bug, but no one on this call has seen it
- Alex says that they're excited about testing of Workspaces/Scratchpad
- asked when the merge will be
- ideally tomorrow, but still needs l10n review and the latest changes
- asked when the merge will be
- Kyle is wondering if there's anyone else from Mozilla in the Web Performance Working Group
- Taras Glek heads up the performance group, but this is low-level
- Chris Blizzard drives product requirements for our platform (standards we need to support as high priority, etc)