Firebug/WeeklyUpdates/2014-05-06

Jan Odvarko, Sebastian Zartner, Florent Fayolle, Joe Walker, Jakob Kaltenbrunner, Belakhdar Abdeldjalil, Simon Lindholm, Christoph Dorn

Holidays

Florent: 6/6 to 6/10

Firebug Releases

• Firebug 2 beta 4
  • Released last Friday
  • Commits: https://code.google.com/p/fbug/issues/list?can=2&q=status%3Acommit&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles
  • We want another beta on Friday as usual

• We might want to have 1.12.9
  • Australis support

Firebug 1.12 blockers

• 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?
• Issue 6557: Font previews don't work
  • We don't want to port to 1.12
  • Florent did great progress

• Issue 6993: The start button icon looks weird in Australis Nightly build
  • We might want to fix this
  • Honza: post screenshot from windows

Firebug 2 Blockers

• Issue 5440: Integrate EventBug into Firebug
  • Let's integrate
  • Florent and Sebastian: please comment fast ;-)
  • Honza: read through and comment too.
  • We want this!
  • Non-element events are open issue. Where/how to display them. Sebastian: file a new issue for this.

• Sebastian: list of extension we want to test with Firebug 2
  • https://docs.google.com/spreadsheet/ccc?key=0ArzNE_OHjXkQdFMySmRxV2xOYjNJTDBZU1BQSk9aS3c&usp=sharing#gid=0
  • Sebastian: prepare new list
  • Honza: review the new list

• Issue 5765: Integrate source maps for JavaScript
  • Farshid: what is the status?

• 1.12 updated to 2.0 breaks the Firebug button
  • The button is not displayed correctly
  • https://code.google.com/p/fbug/issues/detail?id=7444
  • Simon's comment: https://code.google.com/p/fbug/issues/detail?id=4001#c19

• Breakpoint doesn't hit in closures
  • Platform issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1002456

Other Issues

• Issue 6834: Move console grouping repeat number to front of output
  • Several people complained about that in the past - Sebastian
  • We want it for 2.0 only if it's easy to fix

Misc

• Code styling: use [Fx<number>] pattern for comments involving Firefox versions
• Code styling: use [BGZ<number>] pattern for comments involving Bugzilla numbers
• Shortened links: https://bugzil.la/<number>
• Clearer definitions for xxx comments
  • Represents a personal comment
  • Is rather temporary
  • Identifies a problem to solve

• Always use version labels?
  • Yes, even for enhancements, so we have a reference what was the current Firebug version at the moment.

• Getters/setters:
  • We think it's nicer to avoid them in most cases, it's more consistent with current coding style and makes things easier to understand.

FBTest

• Tests causing unresponsive script dialog
  • search/958/

e10s Strategies

Round table discussion

• Honza: suggesting DevTools SDK
  • Initial draft: https://docs.google.com/document/d/1Dr0hFqA6CP9O-Xug5DOYZrrxzsRzbc_xD0mSATn7XcE/edit#

• Florent: https://docs.google.com/document/d/1ALR7awu8nOJFQKFS6DLlMkXBOdjWI8kkf1Agl_QoYlc/edit

Topics for the next meeting

• Issues blocked by 5421
  • http://code.google.com/p/fbug/issues/list?can=2&q=blockedon%3A5421
  • Platform: 5802, 5986, 7055
  • Bug: 1619, 2476, 2912, 4646, 5176, 6205
  • Enhancement: 1238, 2856, 2423, 3639, 4523, 4885, 4995, 6947
  • Arguable: 1185, 1700
  • Review those

• Extension list to test with 2.0

• e10s and the future
  • Make a progress with the documents