Firebug: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Replaced content with '[https://wiki.mozilla.org/Firebug/WeeklyUpdates Firebug Weekly Conference Call Notes] This page originally was used for a different purpose. That content is here: [[SomeOld…')
Line 1: Line 1:
[https://wiki.mozilla.org/Firebug/WeeklyUpdates Firebug Weekly Conference Call Notes]
[https://wiki.mozilla.org/Firebug/WeeklyUpdates Firebug Weekly Conference Call Notes]


(As a point of clarification these are old notes; I don't know the context of their creation. jjb)
This page originally was used for a different purpose. That content is here:
 
[[SomeOldComments]]
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:
* [http://getfirebug.com Firebug Site]
* [https://fireclipse.svn.sourceforge.net/svnroot/fireclipse/trunk/FireclipseExtensions/chromebug/Readme.txt Chromebug Readme]
 
==Potential Integration Issues==
These are issues that could be problematic.
 
===[http://code.google.com/p/fbug/issues/detail?id=97&can=4&q= 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=381223 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.
 
===[https://bugzilla.mozilla.org/show_bug.cgi?id=346664 Bug 346664]===
'''Status:''' See Bug.
 
''' Disucssion:''' See Bug.
 
===[https://bugzilla.mozilla.org/show_bug.cgi?id=344751 Bug 344751]===
'''Status:''' See Bug.
 
''' Disucssion:''' See Bug.
 
===[http://code.google.com/p/fbug/issues/detail?id=159&can=4&q= 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.
 
===[http://code.google.com/p/fbug/issues/detail?id=127&can=4&q= Issue 127 - Firebug memory leak - over 600 MiB seen used]===
'''Status:''' Researching. [http://code.google.com/p/fbug/issues/detail?id=127 FIXED]
 
'''Disucssion:''' Seems to be related to XMLHttpRequests.
 
===[http://code.google.com/p/fbug/issues/detail?id=117&can=4&q= 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?
 
===[http://code.google.com/p/fbug/issues/detail?id=69&can=4&q= Issue 69 - Firebug is enabled always on new tabs]===
'''Status:''' Researching.
 
'''Disucssion:''' See also [https://bugzilla.mozilla.org/show_bug.cgi?id=346664 Bug 346664] and [https://bugzilla.mozilla.org/show_bug.cgi?id=344751 Bug 344751].
 
===[http://code.google.com/p/fbug/issues/detail?id=62&can=4&q= Issue 62 - Step-debug is broken with FireBug on OS X]===
'''Status:''' Researching.
 
'''Disucssion:''' Needs QA.
 
===[http://code.google.com/p/fbug/issues/detail?id=60&can=4&q= 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.  --[[User:Comrade693|Comrade693]] 14:11, 30 May 2007 (PDT)
 
===[http://code.google.com/p/fbug/issues/detail?id=33&can=4&q= Issue 33 - Stepping through JS code crashes Firefox and OS X]===
'''Status:''' Researching.
 
'''Disucssion:''' Needs QA.
 
===[http://code.google.com/p/fbug/issues/detail?id=106&can=4&q= 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.
 
* [http://code.google.com/p/fbug/issues/detail?id=182&can=4&q= Issue 182 - Get firebug to build with Mozilla's build system]
* [http://code.google.com/p/fbug/issues/detail?id=160&can=4&q= Issue 160 - Firebug lacks full chrome under FreeBSD (and probably any platform except Darwin, Linux, linux-gnu, and WINNT)]
* [http://code.google.com/p/fbug/issues/detail?id=175 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.
 
===[http://code.google.com/p/fbug/issues/detail?id=166&can=4&q= 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.
 
===[http://code.google.com/p/fbug/issues/detail?id=52&can=4&q= 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
 
===[http://code.google.com/p/fbug/issues/detail?id=75&can=4&q= Issue 75 - Net monitoring: 404 requests sucking up RAM very bad]===
'''Why not:''' Tomcat: was not able to reproduce this on Windows Vista
 
===[http://code.google.com/p/fbug/issues/detail?id=84&can=4&q= Issue 84 - Crash when inspecting orphaned popup that uses meta refresh]===
'''Why not:''' : Tomcat: no crash on Windows Vista
 
 
===[http://code.google.com/p/fbug/issues/detail?id=87&can=4&q= Issue 87 - Firebug causes firefox to hang]===
'''Why not:''' Tomcat: no crash on Linux Fedora FC6 and FX 2004RC3
 
 
 
===[http://code.google.com/p/fbug/issues/detail?id=139&can=4&q= Issue 139 - 100% CPU and continually incrementing memory usage after closing popup window]===
'''Why not:''' Tomcat: works for me on steps to reproduce
 
===[http://code.google.com/p/fbug/issues/detail?id=153&can=4&q= Issue 153 - clicking on 'HTML' closes Firefox]===
'''Why not:''' Tomcat: no crashs during Tests on Linux
 
===[http://code.google.com/p/fbug/issues/detail?id=147&can=4&q= Issue 147 - Firefox crashes with firebug]===
'''Why not:''' Checked by Tomcat -> no crash
 
===[http://code.google.com/p/fbug/issues/detail?id=142&can=4&q= 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... --[[User:Zeniko|zeniko]] 15:09, 30 May 2007 (PDT)
 
===[http://code.google.com/p/fbug/issues/detail?id=194&can=4&q= 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
[http://getfirebug.com/releases/chromebug  Chromebug]
from the command line this way:
firefox.exe -chrome chrome://chromebug/content/chromebug.xul -firefox

Revision as of 23:15, 4 May 2010

Firebug Weekly Conference Call Notes 

This page originally was used for a different purpose. That content is here:

SomeOldComments

Retrieved from "https://wiki.mozilla.org/index.php?title=Firebug&oldid=220660"