Firebug/1.5

From MozillaWiki
Jump to: navigation, search

1.5 Project Planning

Net Panel

  • Enable panel for offline mode (track cache performance, bug request on file?)
  • Gather feedback from extension developers about possible pain points (YSlow, Pagespeed, HttpWatch, etc)
  • Break-on-XHR (already implemented, seems good so far. Unittests?)
  • MozAfterPaint (draw event lines, explore other UI later)
  • Use activity-observer for precise time measurement (#488270)

Inspect/Net

  • MozAfterPaint overlays?

DOM, CSS

  • Separate sub-tab for CSS (computed vs. original)
    • robcee mentioned he'd like to do this

General

  • Possible problems with globals, refactoring?
  • Remove all 3.0 dependencies

Tabwatcher

  • Remove? Rewrite? - mentioned as a painful area of code that's a continued source of problems. Not sure if this is something we want to tackle for this release or not. Would like some extra risk assessment on this.

Activation Model

  • Done!
    • Honza mentioned a possible solution for different activation systems could be implemented via extension. Mentioned black/whitelist type of extension for managing activation on certain pagesets. Activation Extension API?

Extensions

  • Documentation (what about wiki.getfirebug.com?)
  • Clean up events and naming
  • Chromebug
  • FBTrace included in full release? Mentioned in a news post, need more info.
  • Single-file extensions a-la Jetpack.
  • Can we sort the list of extensions at getfirebug.com/using stats info from addons.mozilla.org? (extensions not available on AMO would be listed at the end)

Website

  • Sort extensions according to some criteria.
    • AMO popularity is one metric. Would be nice to have tie-in and not duplicate existing system.
  • Firebug Collection - setup by Jeff Balogh from moz web team. Offer to help maintain list of extensions.

Testing

  • Http server - move tests to tests.getfirebug.com, use php for dynamic content
  • Add comprehensive AJAXey test suites, jQuery, Dojo, ext.js, moo, etc.
  • Add complex AJAXey sites similar to some problem areas. embedded gMaps, for example.
  • Automated Testsuite
    • already started, need to finish this ASAP for use during 1.5 development.

So, notable missing pieces here are the Script and Console panels. Would like to discuss these in greater detail.