Firebug/WeeklyUpdates/2014-04-29: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Jan Odvarko, Sebastian Zartner, Florent Fayolle, Joe Walker, Jakob Kaltenbrunner, Christoph Dorn, Steven Roussey == Firebug Releases == * Firebug 2 beta 4? ** Honza: do it o...")
 
(Added more links)
 
Line 11: Line 11:
* https://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.12&sort=-id&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles
* https://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.12&sort=-id&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles
* Do we need 1.12.9?
* Do we need 1.12.9?
* Issue 6557: Font previews don't work
* [http://code.google.com/p/fbug/issues/detail?id=6557 Issue 6557]: Font previews don't work
** Florent: summarize the status for the next meeting
** Florent: summarize the status for the next meeting
** Sounds like a blocker for Firebug 2
** Sounds like a blocker for Firebug 2
Line 32: Line 32:
** Honza: (still TODO) give feedback for 1px splitter
** Honza: (still TODO) give feedback for 1px splitter


* Issue 5765: Integrate source maps for JavaScript
* [http://code.google.com/p/fbug/issues/detail?id=5765 Issue 5765]: Integrate source maps for JavaScript
** Farshid is assigned
** Farshid is assigned
** DebuggerLib.getExecutableLines (first try)
** DebuggerLib.getExecutableLines (first try)
** Executable lines + breakpoints + debug location + (error) source links + line numbers + function tooltips (start line + url).
** Executable lines + breakpoints + debug location + (error) source links + line numbers + function tooltips (start line + url).


* Issue 2154: Firebug console and console methods inaccessible from Web Workers ( WebWorkers )
* [http://code.google.com/p/fbug/issues/detail?id=2154 Issue 2154]: Firebug console and console methods inaccessible from Web Workers ( WebWorkers )
** Patch from Simon
** Patch from Simon
** Simon: please address the comments and merge
** Simon: please address the comments and merge
Line 46: Line 46:
** Honza: review the new list
** Honza: review the new list


* Issue 7127: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions"
* [http://code.google.com/p/fbug/issues/detail?id=7127 Issue 7127]: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions"
** Honza: likes the mockup in comment #5
** Honza: likes the mockup in comment #5


== FBTest Harness ==
== FBTest Harness ==
* Sebastian: experiences a crash
* Sebastian: experiences a crash
** TODO: create bugzilla report
** TODO: create bugzilla report


== e10s Strategies ==
== e10s Strategies ==

Latest revision as of 23:23, 30 April 2014

Jan Odvarko, Sebastian Zartner, Florent Fayolle, Joe Walker, Jakob Kaltenbrunner, Christoph Dorn, Steven Roussey


Firebug Releases


Firebug 1.12 blockers


Firebug 2 Blockers

  • Issue 7381: Execution stops on error after reload when 'Break On All Errors' is not active
    • Honza: DONE
  • Issue 7203: A throbber should appear when setting a breakpoint in the Console panel
    • Farshid: status?
  • Issue 5440: Integrate EventBug into Firebug
    • Let's integrate
    • Simon please go ahead!
  • Issue 7082: OSX style issues in new UI
    • Thomas doing great progress
    • Honza: (still TODO) give feedback for 1px splitter
  • Issue 5765: Integrate source maps for JavaScript
    • Farshid is assigned
    • DebuggerLib.getExecutableLines (first try)
    • Executable lines + breakpoints + debug location + (error) source links + line numbers + function tooltips (start line + url).
  • Issue 2154: Firebug console and console methods inaccessible from Web Workers ( WebWorkers )
    • Patch from Simon
    • Simon: please address the comments and merge
  • Issue 7127: Fix "Break On All Errors" in regard of "Break On Exceptions" and "Ignore Caught Exceptions"
    • Honza: likes the mockup in comment #5

FBTest Harness

  • Sebastian: experiences a crash
    • TODO: create bugzilla report

e10s Strategies

Round table discussion

  • Currently there are two main and opposite directions:
    • Keep Firebug separate tool, compete with DevTools (Sebastian, Simon, ...)
    • Do not duplicate features, build on top of DevTools (Honza, Joe, ...)
  • Honza: suggesting DevTools SDK
    • Sebastian: agree
    • Simon: agree too, correct?
  • Next steps:
    • Elaborate more every strategy
    • Everyone should put together a Google doc document with more details about strategy.