Confirmed users
233
edits
Firebug/WeeklyUpdates/2014-02-11: Difference between revisions
Jump to navigation
Jump to search
Firebug/WeeklyUpdates/2014-02-11 (view source)
Revision as of 10:40, 12 February 2014
, 12 February 2014Fixed formatting, added more links
Sebastianz (talk | contribs) (Fixed formatting, added more links) |
|||
| Line 5: | Line 5: | ||
== Releases == | == Releases == | ||
* | * Firebug 1.13 alpha 9 - DONE | ||
* Firebug 1.12.7 | * Firebug 1.12.7 preparation | ||
** Port to 1.12 - Issue 6731: Firebug.getModuleLoaderConfig is not a function | ** Port to 1.12 - Issue 6731: Firebug.getModuleLoaderConfig is not a function | ||
** Remove the JSD always-enabled hack? Yes | ** Remove the JSD always-enabled hack? Yes | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=815603 | ** https://bugzilla.mozilla.org/show_bug.cgi?id=815603 | ||
== Misc == | == Misc == | ||
| Line 17: | Line 16: | ||
== JSD2 Bug Triage == | == JSD2 Bug Triage == | ||
* Issue 7082: OSX style issues in new UI | * [http://code.google.com/p/fbug/issues/detail?id=7082 Issue 7082]: OSX style issues in new UI | ||
** Thomas is working on this | ** Thomas is working on this | ||
** Steven: please review | ** Steven: please review | ||
* Issue 6824: Randomly get "Unresponsive Script Warning" with CommandEditor.html | * [http://code.google.com/p/fbug/issues/detail?id=6824 Issue 6824]: Randomly get "Unresponsive Script Warning" with CommandEditor.html | ||
** Florent | ** Florent is working on this (CM 4 needed) | ||
* Issue | |||
* [http://code.google.com/p/fbug/issues/detail?id=6867 Issue 6867]: Setting conditional breakpoints slows down the execution of the JS | |||
** Honza: mark as commit and create follow up | ** Honza: mark as commit and create follow up | ||
* 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=7097 Issue 7097]: Support for dynamically evaluated scripts | ||
** | ** Honza is working on this | ||
* [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 | |||
** Change the UI? | |||
** Honza: read comments and provide feedback to Sebastian | ** Honza: read comments and provide feedback to Sebastian | ||
* Issue 7169: "Show Stack Trace With Errors" works despite disabled Script panel | * [http://code.google.com/p/fbug/issues/detail?id=7169 Issue 7169]: "Show Stack Trace With Errors" works despite disabled Script panel | ||
** Simon is this a blocker? | ** Simon, is this a blocker? | ||
** We should analyze it | ** We should analyze it | ||
* Issue 7170: Removed commands added for JSD2 debugging | * [http://code.google.com/p/fbug/issues/detail?id=7170 Issue 7170]: Removed commands added for JSD2 debugging | ||
** Simple | ** Simple | ||
* Issue 7169: "Show Stack Trace With Errors" works despite disabled Script panel | * [http://code.google.com/p/fbug/issues/detail?id=7169 Issue 7169]: "Show Stack Trace With Errors" works despite disabled Script panel | ||
** Can we | ** Can we use the debugger when the <em>Script</em> panel is disabled? Probably not. | ||
* Issue 7176: Firebug fails to mark lines as executable when previous line ends a function | * [http://code.google.com/p/fbug/issues/detail?id=7176 Issue 7176]: Firebug fails to mark lines as executable when previous line ends a function | ||
** Honza: analyze this | ** Honza: analyze this | ||
* Issue 7160: The Script panel doesn't scroll properly | * [http://code.google.com/p/fbug/issues/detail?id=7160 Issue 7160]: The Script panel doesn't scroll properly | ||
** If somebody can take this one it would be great | ** If somebody can take this one, it would be great | ||
** Also might have an impact on tests (run entire | ** Also might have an impact on tests (run entire <em>script</em> group, ''script/4724issue4724.js'' fails) | ||
== JSD2 FBTest == | == JSD2 FBTest == | ||
* List of failing tests: https://etherpad.mozilla.org/firebug-fbtest | |||
* Should be our top priority (as soon as all tests pass, we can think about first Firebug 2.0 alpha) | * Should be our top priority (as soon as all tests pass, we can think about first Firebug 2.0 alpha) | ||
* Sebastian: create HTML | * Sebastian: create HTML search failure report | ||
* Issue 7166: Fix FBTests on JSD2 branch | * [http://code.google.com/p/fbug/issues/detail?id=7166 Issue 7166]: Fix FBTests on JSD2 branch | ||
* | * create new tests for specific features and APIs | ||
* | * Remove duplicates? | ||
== DevTools Meeting == | == DevTools Meeting == | ||
* Honza: Portland February 17-21. | * Honza: in Portland February 17-21. | ||
* Usualy kind of a hackaton meeting where everyone is trying to put together something new. | * Usualy kind of a hackaton meeting where everyone is trying to put together something new. | ||
* I'd like to work on PixelPerfect (or support for dynamic scripts JSD2 if ready). It's new, specific feature, devtools don't have it (see http://code.google.com/p/fbug/issues/detail?id=6923) | * I'd like to work on PixelPerfect (or support for dynamic scripts JSD2 if ready). It's new, specific feature, devtools don't have it (see [http://code.google.com/p/fbug/issues/detail?id=6923 issue 6923]) | ||
* Figuring out what new features we could have (for free or low resources), e.g. pretty print, source maps, etc. Sounds like a great opportunity to work on those things, when devtools people are nearby and can help (Simon) | * Figuring out what new features we could have (for free or low resources), e.g. pretty print, source maps, etc. Sounds like a great opportunity to work on those things, when devtools people are nearby and can help (Simon) | ||
* Could we join the meeting? (Florent). Yes, when it's in Europe (yet this year). | * Could we join the meeting? (Florent). Yes, when it's in Europe (yet this year). | ||
== Future Firebug Steps == | == Future Firebug Steps == | ||
| Line 72: | Line 72: | ||
** Expose domain specific features to toolbox (integration) | ** Expose domain specific features to toolbox (integration) | ||
** Reuse existing backend and RDP features | ** Reuse existing backend and RDP features | ||
** Complement not compete | ** Complement, not compete | ||
** User don't | ** User don't want two separate tools | ||
** Firebug has always been an extension after all | ** Firebug has always been an extension, after all | ||
* And we should rather try to add useful, simple, specific tools than advanced features (Simon). | * And we should rather try to add useful, simple, specific tools than advanced features (Simon). | ||
* Devtools try hard to cover every single advanced use-case, like memory profiling etc., and we shouldn't feel the need to do that (Simon). | * Devtools try hard to cover every single advanced use-case, like memory profiling etc., and we shouldn't feel the need to do that (Simon). | ||
* In some sense we want to compete, but with friendly competition, of course. (Simon) | * In some sense we want to compete, but with friendly competition, of course. (Simon) | ||
* My favorite new feature is CSS saving, as you might guess (Simon) | * My favorite new feature is CSS saving, as you might guess (Simon) | ||