Firebug/WeeklyUpdates/2014-03-11: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Jan Odvarko, Sebastian Zartner, Jakob Kaltenbrunner, Florent Fayolle, Simon Lindholm Meeting Agenda: https://etherpad.mozilla.org/firebug == JSD2 Adoption == * JimB working...")
 
(Fixed formatting, corrected spelling and added links)
 
Line 1: Line 1:
Jan Odvarko, Sebastian Zartner, Jakob Kaltenbrunner, Florent Fayolle, Simon Lindholm  
Jan Odvarko, Sebastian Zartner, Jakob Kaltenbrunner, Florent Fayolle, Simon Lindholm, Steven Roussey


Meeting Agenda:
Meeting Agenda:
Line 6: Line 6:
== JSD2 Adoption ==
== JSD2 Adoption ==
* JimB working on introductionType
* JimB working on introductionType
** Bug 982153 - Wrong stack frame lines for scripts dynamically injected using <script> element
** [https://bugzilla.mozilla.org/show_bug.cgi?id=982153 Bug 982153] - Wrong stack frame lines for scripts dynamically injected using <script> element
* Honza: testing the patch and already making changes in Firebug code base.
* Honza: testing the patch and already making changes in Firebug code base.
* Honza: merge issue7097 into jsd2  
* Honza: merge <code>issue7097</code> into <code>jsd2</code>


* newFunction displayURL is asynchronous
* newFunction displayURL is asynchronous
** Bug 981987 - displayURL is not available within Debugger.onNewScript hook for new Function scripts
** ** [https://bugzilla.mozilla.org/show_bug.cgi?id=981987 Bug 981987] - displayURL is not available within Debugger.onNewScript hook for new Function scripts


* JSD1 will be removed from Firefox 31
* JSD1 will be removed in Firefox 31
* 7181: Error breakpoint can't be set
* [http://code.google.com/p/fbug/issues/detail?id=7181 7181]: Error breakpoint can't be set
** Firebug needs modifications
** Firebug needs modifications
** Honza: file a bug
** Honza: file a bug


* Honza: create an issue for:
* Honza: create an issue for:
** JSD1 being deprecated (Firebug should disable the warning message for 29 and 30)
** JSD1 being deprecated (Firebug should disable the warning message for Firefox 29 and 30)
** JSD1 going to be removed (Firebug 1.12 should display a message)
** JSD1 going to be removed (Firebug 1.12 should display a message)


* Issue 7044: Source lines in console should be shown even when Script panel is disabled
* [http://code.google.com/p/fbug/issues/detail?id=7044 Issue 7044]: Source lines in console should be shown even when Script panel is disabled
** Honza: fix this, use the source cache
** Honza: fix this, use the source cache


* Issue 6830: Evaluated expressions should be listed in the Script panel
* [http://code.google.com/p/fbug/issues/detail?id=6830 Issue 6830]: Evaluated expressions should be listed in the Script panel
** Simon put analyses into the issue report, so anyone can understand why we need UI-less support (e.g. why we need it for the backend).
** Simon put analyses into the issue report, so anyone can understand why we need UI-less support (e.g. why we need it for the backend).


== JSD2 FBTest ==
== Firebug 2.0 alpha 1 ==
* Do Firebug 2.0 alpha 1 release in 3 weeks
* Honza: do blogging, new features, asking for feedback
* Honza: hint on AMO, use the 2.0 alpha
* Get 2.0 on AMO soon (as beta 1), to get feedback from beta testers
* Final Firebug 2.0 should be out in 2 months (latest is when Firefox 31 is released)
 
== JSD2 FBTests ==
* Still the top priority
* Still the top priority
* Investigate random failures, find STRs
* Investigate random failures, find STRs
Line 34: Line 41:
* Make FBTest API more solid
* Make FBTest API more solid


== Firebug 2.0 alpha 1 after time ==
=== JSD2 FBTest Failures ===
* Do Firebug 2.0 alpha 1 release in 3 weeks
* Honza: do blogging, new features, asking for feedback
* Honza: hint on AMO, use the 2.0 alpha
* Get 2.0 on AMO soon (as beta 1), to get feedback from beta testers
* Final Firebug 2.0 should be in 2 months (the last time is when Firefox 31 is released)
 
== JSD2 FBTest Failures ==
* See complete info: https://etherpad.mozilla.org/firebug-fbtest
* See complete info: https://etherpad.mozilla.org/firebug-fbtest
* There are failures related to different OSes
* There are failures related to different OSes
Line 67: Line 67:
** Needs instructions
** Needs instructions
** Needs refactoring? (should be a lot simpler)
** Needs refactoring? (should be a lot simpler)
** Let's everyone take a quick look and discuss the next time
** Let's all take a quick look and discuss the next time


* Clipboard testing
* Clipboard testing
** Honza: we might want to have unit test for clipboard (using fake test clipboard for tests)
** Honza: we might want to have a fake test clipboard for tests related to the clipboard avoiding conflicts with the OS clipboard
** http://code.google.com/p/fbug/issues/detail?id=7240 might turn into the fake test clipboard APIs
** http://code.google.com/p/fbug/issues/detail?id=7240 might turn into the fake test clipboard APIs

Latest revision as of 19:38, 11 March 2014

Jan Odvarko, Sebastian Zartner, Jakob Kaltenbrunner, Florent Fayolle, Simon Lindholm, Steven Roussey

Meeting Agenda: https://etherpad.mozilla.org/firebug

JSD2 Adoption

  • JimB working on introductionType
    • Bug 982153 - Wrong stack frame lines for scripts dynamically injected using <script> element
  • Honza: testing the patch and already making changes in Firebug code base.
  • Honza: merge issue7097 into jsd2
  • newFunction displayURL is asynchronous
    • ** Bug 981987 - displayURL is not available within Debugger.onNewScript hook for new Function scripts
  • JSD1 will be removed in Firefox 31
  • 7181: Error breakpoint can't be set
    • Firebug needs modifications
    • Honza: file a bug
  • Honza: create an issue for:
    • JSD1 being deprecated (Firebug should disable the warning message for Firefox 29 and 30)
    • JSD1 going to be removed (Firebug 1.12 should display a message)
  • Issue 7044: Source lines in console should be shown even when Script panel is disabled
    • Honza: fix this, use the source cache
  • Issue 6830: Evaluated expressions should be listed in the Script panel
    • Simon put analyses into the issue report, so anyone can understand why we need UI-less support (e.g. why we need it for the backend).

Firebug 2.0 alpha 1

  • Do Firebug 2.0 alpha 1 release in 3 weeks
  • Honza: do blogging, new features, asking for feedback
  • Honza: hint on AMO, use the 2.0 alpha
  • Get 2.0 on AMO soon (as beta 1), to get feedback from beta testers
  • Final Firebug 2.0 should be out in 2 months (latest is when Firefox 31 is released)

JSD2 FBTests

  • Still the top priority
  • Investigate random failures, find STRs
  • Investigate failures related to Firebug
  • Make FBTest API more solid

JSD2 FBTest Failures

  • console/api/trace.js
  • console/api/exception.js
  • console/api/error.js
  • console/api/assert.js
  • console/4658/issue4658.js
    • Honza: analyze and fix all (related to dynamic scripts + tracing)
  • console/6546/issue6546.js
    • Sebastian: fix this
    • Might be just disabled
  • console/breakOnError/breakOnError.js
    • Florent: fix this
  • firebug/4040/issue4040.js
    • Sebastian: analyze
    • Might be just disabled
  • commandLine/5873/issue5873.js
    • Needs instructions
    • Needs refactoring? (should be a lot simpler)
    • Let's all take a quick look and discuss the next time
Retrieved from "https://wiki.mozilla.org/index.php?title=Firebug/WeeklyUpdates/2014-03-11&oldid=949071"