Firebug/WeeklyUpdates/2013-07-23

Jan Odvarko, Sebastian Zartner, Gal Steinitz, Abdeldjalil Belakhdar

getfirebug.com

• Bug 881896 - Update MediaWiki at getfirebug.com to 1.21.1
  • Sebastian will respond. It's better if Mozilla maintains the wiki (the second suggested option)

Mozilla Summit

• Honza: ask for update

Releases

• Firebug 1.12 beta 4 last week
• Firebug 1.12 beta 5?

Vacation

• Simon: 07/22 - 08/9th

Firebug Lite

• Google event tracking is working.
  • Why users click on "dev" version of FBLite?
  • http://gal.steinitz.com/blog/2013/07/19/remember-firebug-lite/
  • https://getfirebug.com/firebuglite_mobile
  • Next, iPad instructions, new build, ...

Firebug 1.12 Blockers

• Issue 6557: Font previews don't work
  • Converting font response bodies to UTF-8 is wrong
  • Could we keep two versions of the response?
  • Perhaps cache the raw data and convert (and cache converted data) as soon as it's needed?
  • Honza: analyze

• Issue 6336: High CPU usage when showing CSS Layout Box
  • Honza: analyze

Console grouping:

• Issue 6516: Detection of grouped console messages is slow
• Issue 6598: Log groups must not be grouped
• Issue 6602: document.cookie should not group the raw string and the table display
  • Sebastian will take a look
  • We should try to have this in beta 5

• Issue 6597: Console grouping issue with monitorEvents
  • Honza: test on Mac

• Issue 6628: 'Remove cookies' not only removes the cookies shown
  • Only displayed cookies should be removed (depending on path filter)
  • Honza: fix

Extension Testing:

• Progress described in spreadsheet

Miscellaneous:

• Issue 6607: Render issue with search field on MacOS
  • Use PNGs again for now (but the problem is fixed in Firefox 23)
  • Honza test it on Mac

• Move extension issues to github?
  • All agreed we can do it, but not high priority at this point.
  • If possible automatically via port script

• Issue 4938: Firebug hangs the browser on invalid JavaScript (too much recursion)
  • Honza: analyze and try to find a workaround, otherwise wait for JSD2 adoption, which fixes this