Firebug/SomeOldComments

(As a point of clarification these are old notes; I don't know the context of their creation. jjb)

This page is for tracking the integration of Firebug into Firefox.

Questions that need to/should be asked

These need to be addressed sooner rather than later.

• Should we include firebug in moz cvs or keep it as a separate svn repo?
• What does DOMi do that firebug doesn't?
• What does Venkman do that firebug doesn't?
• How would Firebug being included affect web developers?

Related information:

• Firebug Site
• Chromebug Readme

Potential Integration Issues

These are issues that could be problematic.

Issue 97 - Firebug outputs too many warnings in the JS error console

Status: Patch submitted, but unacceptable to project maintainer.

Disucssion: Joe feels that strict mode warnings need to be adjusted, so I filed Bug 381223. I feel that if we are targeting this to web developers, the errors in chrome won't be an issue since those are not displayed by default. However, if we expand the target group to Extension Developers, this will be a serious issue. There are easily over 50 strict warnings with startup alone, so it will be next to impossible for extension authors to find their own strict warnings.

Bug 346664

Status: See Bug.

Disucssion: See Bug.

Bug 344751

Status: See Bug.

Disucssion: See Bug.

Issue 159 - dir("") report String.prototype's defined in other extensions

Status: Researching.

Disucssion: Conflicts with other extensions, especially the Web Developer Extension, aren't good.

Issue 127 - Firebug memory leak - over 600 MiB seen used

Status: Researching. FIXED

Disucssion: Seems to be related to XMLHttpRequests.

Issue 117 - Split browser extension incompatibly

Status: Researching.

Disucssion: This extension (Split Browser) is the culprit. I'm not sure if anything really could be done about this. Perhaps Firebug should disable itself if it detects this extension, with a notification as to why?

Issue 69 - Firebug is enabled always on new tabs

Status: Researching.

Disucssion: See also Bug 346664 and Bug 344751.

Issue 62 - Step-debug is broken with FireBug on OS X

Status: Researching.

Disucssion: Needs QA.

Issue 60 - Firebug doesn't start (throws an exception) when started with frames disabled

Status: Researching.

Disucssion: If this is true, need some kind of workaround. Workaround in bug is probably not acceptable. - Tomcat: Confirmed on Windows and Linux with Firefox 2.0.0.4 RC 3 I have been unable to find a workaround for this. It is quite possible that there isn't one. --Comrade693 14:11, 30 May 2007 (PDT)

Issue 33 - Stepping through JS code crashes Firefox and OS X

Status: Researching.

Disucssion: Needs QA.

Issue 106 - Cannot alt-tab out of Firefox when Firebug is enabled

Cracky: Can confirm that this is definately an issue under Windows XP SP2 + Firebug 1.0.5... Firefox wouldn't alt tab, and after uninstalling Firebug was no longer an issue. However, this is not an issue with my work PC which has similar setup (SP2 and firebug). This was replicated on a clean profile/install of Firefox on my home PC.

In response to... Why not: Tomcat: Works for me on Vista with Firefox 2.0.0.4 RC3 and Firebug 1.0.5

Fixed Issues

These are issues that have patches submitted and committed.

• Issue 182 - Get firebug to build with Mozilla's build system
• Issue 160 - Firebug lacks full chrome under FreeBSD (and probably any platform except Darwin, Linux, linux-gnu, and WINNT)
• Issue 175 - Unable to inspect nested documents created using OBJECT element

Possible Issues to enhance

http://wiki.mozilla.org/User:GijsKruitbosch/JS_Debugging/Tasks

Non-Issues

Issue that were once listed as potential ones or have been concerns people have brought up, but have since been deemed non-issues.

Issue 166 - Without DOM Inspector, message displays HTML code in style window

Why not: I originally misread this as "Firebug requires DOM Inspector. Oops.

Firebug Requires DOM Inspector

Why not: Firebug only uses inIDOMUtils, which, as of Firefox 2.0, is built with layout.

Issue 52 - Firebug crashes FireFox when page is refreshed after setting breakpoint on Vista

Why not: Tomcat: no crash during tests with Windows Vista and Firebug 1.0.5/Firefox 2.0.0.4 RC3

Issue 75 - Net monitoring: 404 requests sucking up RAM very bad

Why not: Tomcat: was not able to reproduce this on Windows Vista

Issue 84 - Crash when inspecting orphaned popup that uses meta refresh

Why not: : Tomcat: no crash on Windows Vista

Issue 87 - Firebug causes firefox to hang

Why not: Tomcat: no crash on Linux Fedora FC6 and FX 2004RC3

Issue 139 - 100% CPU and continually incrementing memory usage after closing popup window

Why not: Tomcat: works for me on steps to reproduce

Issue 153 - clicking on 'HTML' closes Firefox

Why not: Tomcat: no crashs during Tests on Linux

Issue 147 - Firefox crashes with firebug

Why not: Checked by Tomcat -> no crash

Issue 142 - Restore closed tab adds current page to end of history

Why not: Tomcat: sounds more like a Firefox Bug and not a Firebug Bug (yeah, it's a Firefox bug; not sure why I put this here in the first place...)

• WORKSFORME. If this is a Firefox bug, where's the bug number? Rather sounds like an extension incompatibility issue... --zeniko 15:09, 30 May 2007 (PDT)

Issue 194 - Firebug should be able to inspect chrome

Why not: After some discussion with mconnor, it was determined that this would require too much work, and therefore isn't worth it. Chrome developers still have DOMi, which does get some work done on it still.

Or you can run Chromebug from the command line this way:

firefox.exe -chrome chrome://chromebug/content/chromebug.xul -firefox