Firebug/WeeklyUpdates/2014-04-15

Jan Odvarko, Sebastian Zartner, Florent Fayolle, Simon Lindholm, Joe Walker, Steven Roussey, Jakob Kaltenbrunner

Meeting Agenda: https://etherpad.mozilla.org/firebug

Vacations

• Honza: Easter holidays (Friday 18/04 and Monday 21/04)

Firebug Releases

• Firebug 2 beta 2?
  • We could do beta on Thursday
  • Honza: ping me about ideas for blog post topic (related to new features in Firebug 2)

Firebug 2 Extension Compatibility

• We should check the list we have
• Sebastian: get link to the old stylesheet

Firebug 2 Blockers

• Issue 7127: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions"
  • Should be fixed
  • Break on All errors is still enabled in 1.12.8 works
  • What if the "ignore caught exception" wouldn't influence the Break on All errors (as temp solution).
  • We can move "ignore caught exception" into the Console panel.
  • We can move "break on all errors" into the Script panel.

• Make an option that ignores timeouts when Break on Next is activated.
  • Florent: file an issue

• Issue 7203: A throbber should appear when setting a breakpoint in the Console panel
  • Farshid: focus on this one

• Issue 7204: Having an error breakpoint set while 'Break On Exceptions' is checked causes the script execution to stop twice
  • Honza: analyze this

• Issue 7301: Debugger breaks on no more existing breakpoint
• Issue 7340: Undefined context if closed tab is reopened
• Issue 7336: Can't set a breakpoint since client thread is out of sync
  • We don't have STRs for those.

Localization

• Sebastian: Translation and preference naming rules
  • short description for each translation (may be grouped)
  • use camel case with lower case initial
  • don't use underscores or hyphens
  • <key name> for global translations, <module>.<key name> for module specific translations

Firebug strategy & e10s

• https://groups.google.com/forum/#!topic/firebug-working-group/wcCOqyk_kkk
  • Everyone: join the discussion

Strategy suggestions:

Sebastian

Overall strategy:

• Keep Firebug a separate tool but interact with the DevTools
• Rebuild it based on RDP to make it e10s ready
• Use (reworked) APIs of the DevTools as far as possible
• Implement unique but important features to make it outstanding of the other tools

Steps how to reach that goal:

1. Implement a fallback for the case we're not ready when e10s is obligatory (i.e. turn off e10s for Firebug or run it in the client process)
2. Create some general functionality to access the page remotely (I guess that's what Honza calls the SDK)
3. Locate each point where Firebug accesses the page directly
4. Rework the located points, so that they access the page through RDP and e10s messages, first general things like TabWatcher than panel by panel, using DevTools APIs where applicable; while doing that already add some new features
5. Add more new features on top of the new structure

Djalil

Overall strategy:

• Make firebug an advenced debuger (rest client, perf analytics, js game debuger, ...)
• Keep it as simple as now (keep same design)
• Keep existing panel (dont know if it's possible)

Steps how to reach that goal:

1. Integrate devtools, i dont think we have choise, it's not only about e10s but also about all the new things (sourcemap, webgl/ canvas debuging, ...) i know that it's a difficulte decision, for me firebug was a revolutionary tools and now it's time for a new revolution.

Simon

TODO

Florent

TODO

Jakob

TODO

Steven

TODO

Others?

TODO