- This page is intended to summarize plans and directions for Firebug.next
- This summary should also help FWG to prioritize planned steps and features.
- Provide any feedback on Firebug newsgroup
- 1 Status
- 2 Goals for Firebug.next
- 3 New Features for 1.10
- 3.1 Delayed Firebug Load
- 3.2 Orion Text View Integration
- 3.3 Firecookie Integration
- 3.4 Remote HTTP Monitor
- 3.5 Restart-less Firebug Extensions
- 3.6 JSD2
- 3.7 Review Internal File Structure
- 3.8 Style tracing
- 3.9 New Inspector
- 3.10 Net Panel Improvements
- 3.11 HTML entities
- 3.12 Breakpoint Improvements
- 3.13 Group Console Messages
- 4 Implementation
- 5 Further Suggestions
- 6 Open Questions
Current status of Firebug development.
Development frozen on this branch.
Firebug 1.9 is the last released version (available on AMO and getfirebug.com) compatible with Firefox 5-11. Selected patches will be back-ported from 1.10.
Development happens on Firebug 1.10 branch (currently alpha).
Goals for Firebug.next
- Improve memory footprint & performance
- Reuse built-in dev-tools API and components
- Innovate features that only Firebug can deliver
New Features for 1.10
This section lists of all suggested areas FWG should focus on in Firebug 1.10
- Firebug 1.10 blockers
- Memory leaks (Zombie Hunter is necessary)
- Fixing memory leaks is still the top Firebug priority.
Delayed Firebug Load
Firebug UI & Logic is mostly running inside an iframe (chrome://firebug/content/firebugFrame.xul). The goal here is to load the content of the iframe on demand at soon as the user needs Firebug the first time.
However there are some pieces that are running within the global Firefox UI (browser.xul) and must be loaded immediately after the browser window is loaded.
- Page context menu (inspector, open with editor)
- Firebug global menu (tool, view, web developer, ...)
- Firebug start button (Firefox toolbar)
- Firebug iframe and a splitter
Firebug iframe content should be automatically loaded when the user presses F12 or uses any command available through an existing menu or a keyboard shortcut. Such functionality requires all global parts to be clearly separated and independent for the Firebug UI itself (the one running in the iframe).
- Separate Firebug UI from Global UI (create separate directory for global parts)
- Create a command dispatcher for global commands that loads Firebug if necessary.
- Initialize global UI independently of Firebug availability (e.g. translations)
- Adapt to the current
Orion Text View Integration
- Remove all code related to Script panel content generation (firebug/js/sourceBox module)
- Integrate Orion Text View
- Create a new Orion breakpoint ruler
- Support for tooltips displaying result of and evaluated expressions under the mouse (based on Orion Text Styler)
Firecookie is a an extension for Firebug that makes possible to view and manage cookies in your browser.
It was required many times to have such functionality included in Firebug by default.
- Firecookie code base doesn't support AMD
- The code should be divided into more (AMD) modules
- Support for backward compatibility can be removed
- Blocking issues should be fixed
- Firecookie automated tests should be merged into Firebug test list
Remote HTTP Monitor
The Net panel should use Remote Debugging Protocol (RDP) to communicate with the server side that is performing HTTP monitoring. This should enabled remote HTTP monitoring e.g. for mobile devices.
The server side script should be using the following interfaces (to monitor HTTP):
- nsIWebProgressListener (monitors the file:/// protocol)
- nsIObserver (monitors http-on-* events to catch also BFCache responses)
- nsITraceableChannel (intercepts response bodies)
- Define new actors and extend the RDP protocol
- Clean separation of the client and server parts
- Communication between client and server based on JSON packets
Restart-less Firebug Extensions
There should be a way how to install Firebug and extensions without Firefox restart. Some API related to dynamic registration are already available.
- Review API for dynamic adding/removal of panels
- Review API for dynamic adding/removal of modules
- Review extension example
- Update documentation/tutorial
JSD2 (also known as JSDBG2 or JSDBGAPI) represents new API for JS debugging in Firefox.
Jim Blandy and Jason Orendorff are working on a JS implementation of JSD built on top of the JSDBG2 API (a wrapper). This wrapper should be injected into Firebug and make it compatible with JSDBG2. Prototype implementation is available (Firebug 1.9 fork).
Work on this goal depends on how much ready JSD2 is.
Review Internal File Structure
If parts break extensions, they will go into 2.0.
- Convert last few files into (AMD) modules
- Split huge files into more modules
- Suggest places/modules that needs refactoring (e.g. TabWatcher)
The CSS Panel should offer a different view on CSS properties to allow to find out how a specific value was generated.
- Investigate built-in CSS API
- Create a new property-based view for the CSS panel using the built-in CSS API
- Add option to the CSS panel to toggle between the current view and the property-based view
- Add display of assigned properties, which can be expanded to see the trace
- Allow disabling of single styles in the trace and the complete style trace
Firebug should reuse the existing built-in Inspector to avoid conflicts with the page styles.
Net Panel Improvements
Proposed Net panel improvements
- Net panel header should not scroll.
The HTML Panel needs different options how entities are displayed.
There should be three display options inside the HTML panel's options menu:
- Show Entities as Symbols
- Show Entities as Names
- Show Entities as Unicode
- Find out how the API is working exactly
- Implement new mapping function in
lib/string.jsincluding the API
- Implement the new options
Several new features related to breakpoints should be introduced. It should be possible to specify how many times a breakpoint should be hit before it breaks the script execution as well as to create and edit breakpoint conditions in the Breakpoints Side Panel.
- Change the Breakpoints side panel to allow inline editing (required for the other tasks)
- Hit count for breakpoints
- Implement hit count into debugger
- Add hit count to Breakpoints side panel
- Move breakpoint condition editing to the Breakpoints side panel
- Add breakpoint condition to Breakpoints side panel
- Add context menu to Breakpoint Column containing option to edit the condition
Group Console Messages
Console messages optionally need to be grouped to avoid spamming the Console Panel.
- Group error messages
- Group messages produced by the 'console' object
See the following table that summarizes list of features and dev folks working on them. Append yourself as a developer to features you are interested in to participate.
|Delayed Firebug Load||Honza, Harutyun?||Issue 4989: Separate global UI (browser.xul) from Firebug UI (firebugFrame.xul)|
|Remote HTTP Monitor||Honza||TODO|
|Restart-less Firebug Extensions||Honza||TODO|
|Review Internal File Structure||Honza, Sebastian||Issue 4960: Review internal file structure|
|Style Tracing||Sebastian||Issue 2916: Trace Styles Feature|
|New Inspector||Sebastian||Issue 4848: Create new SVG inspector|
|Net Panel Improvements||-||Issue 2617: Net panel header should be fixed on top instead of scrolling with the content|
|HTML Entities||-||Issue 3159: Show numeric character reference of MathML|
|Breakpoint Improvements||-|| Issue 4378: Move editing of breakpoint conditions to Breakpoints Side Panel
Issue 2817: Hit counts for breakpoints
|Group Console Messages||-||Issue 4979: Group console messages|
Please append further suggestions for new 1.10 features in this section so. We'll yet discuss all these suggestions.
Better user feedback
This has been already discussed before. It could be useful to have more feedback from Firebug users and use it for targeted improvements. The feedback should be collected using Testpilot and its related infrustructure and/or through a Firebug extension.
- What specific data should be collected?
- What kind of knowledge we can get from the collected data?
Mapping of URLs to file system paths
Firebug currently doesn't have any connection to the server files. Many people don't understand that and they are asking how to achieve that. This change would at least allow mapping between local server URLs and the file system.
- How is this related to Firediff?
- Apart from Firecookie integration, are there any other extensions we would like to distribute with Firebug by default? (e.g. EventBug, FireStarter, NetExport, ...).
- What further API/Components related to built-in dev tools could be reused by Firebug?