Firebug: Difference between revisions

Latest revision as of 08:24, 25 July 2012

This page is for Mozilla - Firebug Coordination.

Firebug And Bugzilla

When filing new Bugzilla bugs that affect Firebug, add a whiteboard entry using the following guidelines:

[firebug-p1] - Bad crashes and security issues, blockers, major features
[firebug-p2] - Important issues we need to make progress on
[firebug-p3] - Tracking related to Firebug

Planning: Wishlists

Planning: Firebug versions

Firebug Roadmap

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

@@ Line 1: / Line 1: @@
-This page is for tracking the integration of Firebug into Firefox.
+This page is for Mozilla - Firebug Coordination.
-==Potential Integration Issues==
+* [https://wiki.mozilla.org/Firebug/WeeklyUpdates Firebug Weekly Conference Call Notes]
-These are issues that could be problematic.
+* [http://code.google.com/p/fbug/issues/list?can=2 Firebug issues list]
+* [https://groups.google.com/forum/#!forum/firebug Firebug discussion group]
+* [https://getfirebug.com/wiki Firebug wiki]
-===[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]===
+== Firebug And Bugzilla ==
-'''Status:''' Patch submitted, but unacceptable to project maintainer.
+When filing new Bugzilla bugs that affect Firebug, add a whiteboard entry using the following guidelines:
-'''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].
+* <code>[firebug-p1]</code> - Bad crashes and security issues, blockers, major features
-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.
+* <code>[firebug-p2]</code> - Important issues we need to make progress on
+* <code>[firebug-p3]</code> - Tracking related to Firebug
-==Fixed Issues==
+== Planning: Wishlists ==
-These are issues that have patches submitted and committed.
+* [[Firebug: Mozilla Wish List]]
+* [http://code.google.com/p/fbug/issues/list?can=2&q=Type%3DEnhancement Firebug Enhancement Requests]
-* [http://code.google.com/p/fbug/issues/detail?id=182&can=4&q= Issue 182 - Get firebug to build with Mozilla's build system]
+== Planning: Firebug versions ==
+* [http://getfirebug.com/wiki/index.php/Firebug_Roadmap Firebug Roadmap]
-== Possible Issues to enhance ==
+----
-http://wiki.mozilla.org/User:GijsKruitbosch/JS_Debugging/Tasks
-==Non-Issues==
+This page originally was used for a different purpose. That content is here:
-Issue that were once listed as potential ones or have been concerns people have brought up, but have since been deemed non-issues.
+[https://wiki.mozilla.org/index.php?title=Firebug&oldid=175216]
-===[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.