Firebug/WeeklyUpdates/2012-05-15: Difference between revisions
< Firebug | WeeklyUpdates
Jump to navigation
Jump to search
Sebastianz (talk | contribs) (Added myself as participant; fixed several descriptions) |
|||
| Line 1: | Line 1: | ||
Jan Odvarko, Joe Walker, Steven Roussey | Jan Odvarko, Joe Walker, Sebastian Zartner, Steven Roussey | ||
== Firebug 1.10 == | == Firebug 1.10 == | ||
* 1.9.2 out (still waiting on AMO review) | * 1.9.2 out (still waiting on AMO review) | ||
* 1.10a8 out | * 1.10a8 out | ||
* List of | * List of [http://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.10 1.10 blockers] | ||
== Trace Styles Feature == | == Trace Styles Feature == | ||
Sebastian made great progress on [http://code.google.com/p/fbug/issues/detail?id=2916 issue 2916] and refactored the Computed side panel: | Sebastian made great progress on [http://code.google.com/p/fbug/issues/detail?id=2916 issue 2916] and refactored the Computed side panel: | ||
* Computed Side panel | * Computed Side panel is empty when reloading page with local file | ||
** Related to csslogic module | ** Related to csslogic module | ||
* Style menu missing | * Style panel context menu missing editing element style option fixed. | ||
== Memory Leaks == | == Memory Leaks == | ||
* Since [https://bugzilla.mozilla.org/show_bug.cgi?id=695480 Bug 695480] (Remove support for Chrome -> Content leaks) is fixed | * Since [https://bugzilla.mozilla.org/show_bug.cgi?id=695480 Bug 695480] (Remove support for Chrome -> Content leaks) is fixed there doesn't seem to be any zombie compartments any more. Anyone could retest? | ||
== getfirebug.com == | == getfirebug.com == | ||
| Line 22: | Line 19: | ||
** Does this make sense? | ** Does this make sense? | ||
** We need different folder for different Firebug versions | ** We need different folder for different Firebug versions | ||
** Honza: kick off a thread on FWG | ** Honza: kick off a thread on FWG | ||
== HTTP Monitor == | == HTTP Monitor == | ||
* Further details related to remote debugging fixed | * Further details related to remote debugging fixed | ||
== Firebug Remote Debugging UI == | == Firebug Remote Debugging UI == | ||
* [https://groups.google.com/forum/?fromgroups#!topic/firebug-working-group/oVZhRgSh_b4 Thread in the discussion group] | * [https://groups.google.com/forum/?fromgroups#!topic/firebug-working-group/oVZhRgSh_b4 Thread in the discussion group] | ||
* Honza: start a thread about remote architecture UI and create a wiki page. | * Honza: start a thread about remote architecture UI and create a wiki page. | ||
== Automated Tests == | == Automated Tests == | ||
| Line 40: | Line 34: | ||
== AMD approach == | == AMD approach == | ||
* It's ok to define more objects in | * It's ok to define more objects in one AMD module | ||
* The file shouldn't be too big (thousands of lines is big) | * The file shouldn't be too big (thousands of lines is big) | ||
* Update | * Update [http://getfirebug.com/wiki/index.php/Firebug_Coding_Style code style page] | ||
Latest revision as of 20:23, 15 May 2012
Jan Odvarko, Joe Walker, Sebastian Zartner, Steven Roussey
Firebug 1.10
- 1.9.2 out (still waiting on AMO review)
- 1.10a8 out
- List of 1.10 blockers
Trace Styles Feature
Sebastian made great progress on issue 2916 and refactored the Computed side panel:
- Computed Side panel is empty when reloading page with local file
- Related to csslogic module
- Style panel context menu missing editing element style option fixed.
Memory Leaks
- Since Bug 695480 (Remove support for Chrome -> Content leaks) is fixed there doesn't seem to be any zombie compartments any more. Anyone could retest?
getfirebug.com
- Bug 743930 - Properly sync getfirebug.com with source base from GIT
- Does this make sense?
- We need different folder for different Firebug versions
- Honza: kick off a thread on FWG
HTTP Monitor
- Further details related to remote debugging fixed
Firebug Remote Debugging UI
- Thread in the discussion group
- Honza: start a thread about remote architecture UI and create a wiki page.
Automated Tests
- Clint Talbert, work still in-progress
- Mochitest needs Firefox source & build.
- Mike: adopting Net panel tests to mochitest, wait for his results
AMD approach
- It's ok to define more objects in one AMD module
- The file shouldn't be too big (thousands of lines is big)
- Update code style page