Firebug/WeeklyUpdates/2008-12-09
From MozillaWiki
< Firebug | WeeklyUpdates
Contents
Attendees
curtisb, janodvarko, johnresig, steves, robc
Upcoming events
- Steve Souders mentioned the Velocity Conference in San Jose for June, calls for topics in the air. Steve to send Jresig an email.
getfirebug.com
- DONE - add blog link to planet
- todo - Kohei to translate Japanese getfirebug.com pages. In progress.
Localization
- Couple of new translators and many updates + New Locale ro-RO (Romanian).
- Italian and German locales in progress.
Net Panel
- honza working on gathering comprehensive list of MIME types for dealing with binary files. Needs to prevent them from being cached.
- todo find canonical list in firefox codebase - robcee
- cache fix in firebug 1.4. needs testing.
Fireunit
- DONE - push new API changes (jresig)
- should be ready to go, just waiting on some security review, but otherwise useable.
- net tests and fixes (honza)
- jresig still has some security concerns re: activation of webserver
- OK if called from chrome or file, not so if remote
- need a UI to locate list of tests
Extensions
- steve reminded us about Christoph Dorn, and will invite him to next week's meeting. He's interested on documenting Firebug extension development and possibly creating / hosting example code on github.
Activation UI
- robc attempted to recap emails, recommends simplifying rather than adding new UI.
- curtis raised the comment about using different (ffx) profiles for testing/debugging. robc suggests that's probably a small number of users.
- steves asked some local devs a few questions about what sites were enabled in their browsers with firebug. Those who did know that firebug was enabled, couldn't tell for which sites it was turned on.
- honza suggests we're working on opposing goals. People want a Big Button.
- robc mentioned that even if we go to a big button, we'll still have the mini drop-down menus for turning features on or off. steves suggests that the minimenus are not visible enough. should be tweaked to be more visible/obvious.
- curtis suggests asking users up front about what type of user they are (designer vs coder) to setup firebug on first use. Hiding script, console and net if a user doesn't want them.
- robc has also suggested something similar for the tabstrip, with a button to turn on code panels, leaving them off most of the time.
- steves asked about issue 1176, suspend/resume state on session restart
- jresig thinks we should try to simplify. Promote using a separate profile and further explain and document the activation process and why it exists.
- to follow up in an email thread, hopefully with mockups.
email notes from JohnJB
1.4 news
- a8 out
- group eval/event file names with parent file name in filelists on Script panel
- initial implementation decompileEvals option on Script panel (ok for sanity check, curiousity, not for development)
- initial implementation of traceCalls(fn) (works, output broken)
- initial implementation of traceAll() (crashes FF)
- I can be done with 1.4 anytime, these three initial implementations could be moved to 1.5.
FF3.1
- still stuck on FF3.1 bugs
jsd2
- no progress, except to switch dev to FF3.1 tree (off new FF3.2 branch).
Firebug 1.3
- one more beta! release next week?
Firebug 1.4
- move to beta when 1.3 released
Chromebug 0.4a2
- possibly broken focus on Mac, jjb to investigate, robcee to try to verify.
- seems wonky, but I think it's expected (robc)
- based on firebug 1.4 now
Firefox
- jsd2 work can begin - jjb
- bugzilla cleanup for 2.0-only problems.
- chromebug in firefox 3.1 is opening 0-size windows
- bug 465993 Blocks chromebug on FF3.1
- todo need someone to install the test case and verify - robcee
- new jsd tests: /fbug/chromebug/tests/jsdTests@johnjbarton.com
- need someone to install this extension in an clean Firefox profile (no Firebug) and try it.
- bug 379410 (jsdICompilationUnit) First work in progress patch. reworked the test case: fbug/chromebug/tests/jsdTests@johnjbarton.com/content/jsd/jsdIDebuggerService2/bugzilla-379410.js
- bug 449454 Work abandoned, Lower priority now since 379410 will do the work.
- Bugs against jsd:
- Top priority, causes erroneous application behavior: https://bugzilla.mozilla.org/show_bug.cgi?id=463239
- Causes un-debuggable code: https://bugzilla.mozilla.org/show_bug.cgi?id=462704
- Both of these have test cases in fbug/chromebug/tests/jsdTests@johnjbarton.com/content/jsd/jsdIScript