Firebug/WeeklyUpdates/2014-02-11

Jan Odvarko, Sebastian Zartner, Jakob Kaltenbrunner, Simon Lindholm, Florent Fayolle, Belakhdar Abdeldjalil

Releases

DONE Firebug 1.13 alpha 9
Firebug 1.12.7 Preparation
- Port to 1.12 - Issue 6731: Firebug.getModuleLoaderConfig is not a function
- Remove the JSD always-enabled hack? Yes
- https://bugzilla.mozilla.org/show_bug.cgi?id=815603

Issue 7082: OSX style issues in new UI
- Thomas is working on this
- Steven: please review

Issue 6824: Randomly get "Unresponsive Script Warning" with CommandEditor.html
- Florent: is working on this (CM 4 needed)
Issue 6824: Randomly get "Unresponsive Script Warning" with CommandEditor.html
- Honza: mark as commit and create follow up
Issue 7097: Support for dynamically evaluated scripts
- Honza working on this.

Issue 7127: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions
- Keep the UI as it is
- Fix the conflict
- Honza: read comments and provide feedback to Sebastian

Issue 7170: Removed commands added for JSD2 debugging
- Simon is this a blocker?
- We should analyze it?

Issue 7169: "Show Stack Trace With Errors" works despite disabled Script panel
- Can we used Debugger when the Script panel is disabled? Probably not

Issue 7176: Firebug fails to mark lines as executable when previous line ends a function
- Honza: analyze this

Issue 7160: The Script panel doesn't scroll properly
- If somebody can take this one it would be great
- Also might have an impact on tests (run entire Script group, 4724 fails)

Should be our top priority (as soon as all tests pass, we can think about first Firebug 2.0 alpha)
Sebastian: create HTML Search failure report
Issue 7166: Fix FBTests on JSD2 branch
creating new tests
Removing duplicates?

Honza: Portland February 17-21.
Usualy kind of a hackaton meeting where everyone is trying to put together something new.
I'd like to work on PixelPerfect (or support for dynamic scripts JSD2 if ready). It's new, specific feature, devtools don't have it (see http://code.google.com/p/fbug/issues/detail?id=6923)

Figuring out what new features we could have (for free or low resources), e.g. pretty print, source maps, etc. Sounds like a great opportunity to work on those things, when devtools people are nearby and can help (Simon)
Could we join the meeting? (Florent). Yes, when it's in Europe (yet this year).

After JSD2 is in place (Firebug 2.0), we need to think about full RDP support (all panels). The current (rough) estimate is that electrolysis (e10s) could be ready in 12 months. There will be fall-back support for some time (switching off e10s)
Basics:
- Focus on domain specific features (like e.g. PixelPerfect, jQuery, etc.)
- Expose domain specific features to toolbox (integration)
- Reuse existing backend and RDP features
- Complement not compete
- User don't wont two separate tools
- Firebug has always been an extension after all
And we should rather try to add useful, simple, specific tools than advanced features (Simon).
Devtools try hard to cover every single advanced use-case, like memory profiling etc., and we shouldn't feel the need to do that (Simon).
In some sense we want to compete, but with friendly competition, of course. (Simon)
My favorite new feature is CSS saving, as you might guess (Simon)