Firebug/WeeklyUpdates/2014-07-08: Difference between revisions
< Firebug | WeeklyUpdates
Jump to navigation
Jump to search
(Created page with "Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm == Vacations == == Firebug 2 == * https://code.google.com/p/fb...") |
Sebastianz (talk | contribs) (Linked issues, corrected spelling mistakes and added more info) |
||
| Line 1: | Line 1: | ||
Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm | Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm | ||
== Firebug 2 == | == Firebug 2 == | ||
* https://code.google.com/p/fbug/issues/detail?id=7560 (Improve performance of switching between JavaScript sources) | * [https://code.google.com/p/fbug/issues/detail?id=7560 Issue 7560] (Improve performance of switching between JavaScript sources) | ||
** Probably related to syntax highlighting; many complaints => high priority | ** Probably related to syntax highlighting; many complaints => high priority | ||
** Introduce a new option in the Firebug menu "Turn off Color Highlighting" | ** Introduce a new option in the Firebug menu "Turn off Color Highlighting" | ||
** Switch off syntax color everywhere | ** Switch off syntax color everywhere (Script panel, Edit Mode of CSS and HTML panel, Command Editor) | ||
** | ** Create a test case with a huge JS file to see the performance problem | ||
** But first: we should try appending the stylesheet asynchronously | ** But first: we should try appending the stylesheet asynchronously | ||
** Farshid: take a look at that | ** Farshid: take a look at that | ||
| Line 15: | Line 12: | ||
** (Honza can introduce you if you want :) | ** (Honza can introduce you if you want :) | ||
* [https://code.google.com/p/fbug/issues/detail?id=7301 Issue 7301] (Debugger breaks on no more existing breakpoint) | |||
* https://code.google.com/p/fbug/issues/detail?id=7301 (Debugger breaks on no more existing breakpoint) | |||
** Honza: take a look | ** Honza: take a look | ||
** There is no test case | ** There is no test case | ||
* https://code.google.com/p/fbug/issues/detail?id=7512 (Hitting a breakpoint causes minimized Firefox browser windows to maximize) | * [https://code.google.com/p/fbug/issues/detail?id=7512 Issue 7512] (Hitting a breakpoint causes minimized Firefox browser windows to maximize) | ||
* https://code.google.com/p/fbug/issues/detail?id=7515 (Breakpoint doesn't get hit on frames) | * Needs more investigation of Windows devs | ||
* https://code.google.com/p/fbug/issues/detail?id=7586 (Breakpoint doesn't get hit reloading | |||
* [https://code.google.com/p/fbug/issues/detail?id=7515 Issue 7515] (Breakpoint doesn't get hit on frames) | |||
* [https://code.google.com/p/fbug/issues/detail?id=7586 Issue 7586] (Breakpoint doesn't get hit reloading | |||
** Sebastian: provide a test case | ** Sebastian: provide a test case | ||
** Honza: provide a patch | ** Honza: provide a patch | ||
== Firebug 3 == | == Firebug 3 == | ||
* Theming | * Theming | ||
** Let focus on one "Firebug" theme and do it right | ** Let focus on one "Firebug" theme and do it right | ||
** We can safe reasonable amount of time by not maintaining three different themes. | ** We can safe a reasonable amount of time by not maintaining three different themes. | ||
** But, it may be a competitive advantage for Firebug | ** But, it may be a competitive advantage for Firebug to have different themes. | ||
* Use chrome.manifest file | * Use chrome.manifest file | ||
| Line 44: | Line 41: | ||
** No blocker apart from accessing the locale dir | ** No blocker apart from accessing the locale dir | ||
* Let's use "theme" label for all new | * Let's use a "theme" label for all new issues related to theming stuff | ||
* Simplify error tracing API | * [https://github.com/firebug/firebug.next/issues/17 Issue 17]: Simplify error tracing API | ||
** Options for short API: | ** Options for short API: | ||
** TraceError.sysout() | ** TraceError.sysout() | ||
| Line 53: | Line 50: | ||
** Florent: make a decision | ** Florent: make a decision | ||
* https://github.com/firebug/firebug.next/issues/5 | * [https://github.com/firebug/firebug.next/issues/5 Issue 5]: Github Issues need discussion because of some difference with one used for Firebug 2 | ||
** All: | ** All: everyone should read and comment | ||
Demo for London work week (milestone "london" - we want this milestone in the github.com issue list), focus on (can we have meta bugs?): | Demo for London work week (milestone "london" - we want this milestone in the github.com issue list), focus on (can we have meta bugs?): | ||
Latest revision as of 12:52, 9 July 2014
Jan Odvarko, Joe Walker, Florent Fayolle, Sebastian Zartner, Farshid Beheshti, Steven Roussey, Simon Lindholm
Firebug 2
- Issue 7560 (Improve performance of switching between JavaScript sources)
- Probably related to syntax highlighting; many complaints => high priority
- Introduce a new option in the Firebug menu "Turn off Color Highlighting"
- Switch off syntax color everywhere (Script panel, Edit Mode of CSS and HTML panel, Command Editor)
- Create a test case with a huge JS file to see the performance problem
- But first: we should try appending the stylesheet asynchronously
- Farshid: take a look at that
- Farshid: ask :bgrins in #devtools IRC (Brian Grinstead, CM guru)
- (Honza can introduce you if you want :)
- Issue 7301 (Debugger breaks on no more existing breakpoint)
- Honza: take a look
- There is no test case
- Issue 7512 (Hitting a breakpoint causes minimized Firefox browser windows to maximize)
- Needs more investigation of Windows devs
- Issue 7515 (Breakpoint doesn't get hit on frames)
- Issue 7586 (Breakpoint doesn't get hit reloading
- Sebastian: provide a test case
- Honza: provide a patch
Firebug 3
- Theming
- Let focus on one "Firebug" theme and do it right
- We can safe a reasonable amount of time by not maintaining three different themes.
- But, it may be a competitive advantage for Firebug to have different themes.
- Use chrome.manifest file
- For skin dirs
- For locale dirs
- Honza: take a look
- Default arg values
- Yes, please!
- Localization API (Farshid)
- No blocker apart from accessing the locale dir
- Let's use a "theme" label for all new issues related to theming stuff
- Issue 17: Simplify error tracing API
- Options for short API:
- TraceError.sysout()
- TraceError.syserr()
- TraceError.log()
- Florent: make a decision
- Issue 5: Github Issues need discussion because of some difference with one used for Firebug 2
- All: everyone should read and comment
Demo for London work week (milestone "london" - we want this milestone in the github.com issue list), focus on (can we have meta bugs?):
- Firebug theme
- Support for jQuery
- Server side logging