Confirmed users
837
edits
Firebug/WeeklyUpdates/2014-04-22: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Jan Odvarko, Sebastian Zartner, Florent Fayolle, Simon Lindholm, Joe Walker, Jakob Kaltenbrunner, Christoph Dorn, Belakhdar Abdeldjalil | |||
== Firebug Releases == | == Firebug Releases == | ||
* Firebug 2 beta 3 | * Firebug 2 beta 3 | ||
** Honza: do release on Friday | |||
** Everyone: tips for blog post news | |||
== Firebug 2 Blockers == | == Firebug 2 Blockers == | ||
* Issue 7381: Execution stops on error after reload when 'Break On All Errors' is not active | |||
** Honza: take a look | |||
* [http://code.google.com/p/fbug/issues/detail?id=7203 Issue 7203]: A throbber should appear when setting a breakpoint in the Console panel | * [http://code.google.com/p/fbug/issues/detail?id=7203 Issue 7203]: A throbber should appear when setting a breakpoint in the Console panel | ||
** Farshid: status? | ** Farshid: status? | ||
* Issue 7127: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions" | |||
** If anyone has any suggestions, please post a comment. | |||
** The "Break on All Errors" could be disabled when "Break on all exceptions" is on. | |||
* Sometimes it is not possible to create a breakpoint | |||
** Honza: needs STRs | |||
** There is an exception in the tracing console | |||
* Issue 5440: Integrate EventBug into Firebug | |||
** Should we add it into Firebug 2? | |||
** Simon: do some test case + instructions + list of all features | |||
** Anything not finished? | |||
== e10s Strategies == | == e10s Strategies == | ||
| Line 68: | Line 83: | ||
# Use existing e10s infrastructure from native tools through SDK. | # Use existing e10s infrastructure from native tools through SDK. | ||
# Build unique features on top of the SDK | # Build unique features on top of the SDK | ||
=== Simon === | |||
Overall strategy: | |||
* compete with native tools (we are established, have a nice UI, and our base functionality - which is what matters most - is really solid; hence I think we can be successful in doing this) | |||
* build parts of Firebug on top of devtools backend, to move faster (and get closer to remoting) | |||
* focus on unique features | |||
Steps how to proceed: | |||
# Investigate running Firebug in the content process, or otherwise find workarounds for e10s. Much of what strategy to choose hinges on this. IMO no other solution will be ready in the right time frame, and we'll still have users wanting to continue use the original Firebug, so this is critical is either case. Assuming we can cope: | |||
# Slowly move towards remoting by rebuilding on top of devtools backend. | |||
# Build some new features ourselves, and others (e.g. clones of new features) with help of devtools APIs. | |||