getfirebug.com has Firebug 1.4a14

[John J Barton]

I just finished a blog post about the new enablement approach in
Firebug 1.4,
http://blog.getfirebug.com/?p=124

1.4a14 has this new approach implemented and we'd be interested in
feedback.
http://getfirebug.com/releases

jjb

[niver]

I'm not sure about this new enablement approach, since v1.4a14 (X or
not) crashes my Firefox (3.0.7, winxp, clean profile) each time I try
to open the Firebug panel. I happened to be able to open it once, but
Firefox crashed as soon as I tried to disable the Script tab.

N.

On Mar 25, 8:56 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> I just finished a blog post about the new enablement approach in

> Firebug 1.4,http://blog.getfirebug.com/?p=124

[BB]

Yes, Firefox 3.1b3 crashes, too, if I want to open firebug...

[johnjbarton]

Please use about:crashes to get the crash URLs and post them.

The only crash of Firefox that I have know about is with debug builds
of Firefox.

jjb

[Maciej Jaros]

johnjbarton pisze:

> Please use about:crashes to get the crash URLs and post them.
>
> The only crash of Firefox that I have know about is with debug builds
> of Firefox.
>

On an almost clean profile:
http://crash-stats.mozilla.com/report/index/7b2951f8-25d1-494d-aa4f-73c652090326

Firebug opened from:
http://www.google.pl/firefox?client=firefox-a&rls=org.mozilla:pl:official
(but I was unable to open it on other pages too)

Regards,
Nux.

[Maciej Jaros]

johnjbarton wrote:
> Please use about:crashes to get the crash URLs and post them.
>
> The only crash of Firefox that I have know about is with debug builds
> of Firefox.
>

got it:
1) if you click RMB and select disable all, and then click LMB you'll crush
2) if you click RMB and select enable all, and then click LMB you'll get
the Firebug window

1) "works" even if you'll do it after 2).

[Maciej Jaros]

Kids don't try this at home ;-). Now I cannot open this profile
(fortunately a testing profile).

[johnjbarton]

I can't get this to happen with FF3.0.7 or FF3.1b3 and Firebug 1.4a14.
Anyone else see this crash?

jjb

[Maciej Jaros]

johnjbarton wrote:
> I can't get this to happen with FF3.0.7 or FF3.1b3 and Firebug 1.4a14.
> Anyone else see this crash?
>

One more thing... When I do:

1. Enable panels
2. Open FB
3. Close FB
4. Disable panels

It all starts to work (I can disable and open), but then after I:

1. Close browser window
2. Start a browser (with "-p" BTW).
3. Open FB

It still crushes (I use Polish version if that makes any difference).

[Jan Odvarko]

I have reported a bug here:
https://bugzilla.mozilla.org/show_bug.cgi?id=485511

It looks like the problem is only with localized version of Firefox.
Was anybody able to reproduce that with en-US version?

I have committed a workaround into 1.4 (R2320) to solve it for now.
Should be part of Firebug 1.4a15 (as soon as it's available).

Honza

[niver]

I can confirm the R2320 commit fixes the problem for me (using fr-CA
firefox).

Do you plan to fix the localized display for disabled panels? Anything
we can do to help to translate that "desc3" placeholder?

N.

[alfonsoml]

I think that the "autodisable" of firebug will bring lots of reports
about broken functionality.
Since the very beginning of firebug I was able to set the domains that
I'm working on, and without the need to keep firebug open I was able
to quickly see any javascript error in the status bar. At that moment
I open Firebug and check what's the error and start the debugging.
Now I'm finding myself that sometimes a page doesn't work, but I don't
see any warning, so I fire up IE8 and it quickly shows a dialog
informing of the problem and the ability to debug it. Even using the
most basic installation of IE6 anyone is able to see the exclamation
icon in the status bar informing of the error.

On 26 mar, 02:56, John J Barton <johnjbar...@johnjbarton.com> wrote:
> I just finished a blog post about the new enablement approach in

> Firebug 1.4,http://blog.getfirebug.com/?p=124

[johnjbarton]

Yes all of the localizations will be updated, but we want to get
feedback on the en-US text before we ask localizers to translate.

jjb

[johnjbarton]

We could report errors in the status bar, but not without adding
overhead to every page load.
jjb

[alfonsoml]

If I have choose to install Firebug and enable the console and script
panel for some domains, I guess that it should be a safe bet that I'm
interested about any errors in those pages, even if they mean some
extra overhead for the pages that I'm working on.
I can understand for example that in order to get correct data in the
net panel I might need to first show that panel and then reload the
page, but always showing the errors in the status bar, as long as the
console and script panel is enabled for a domain, seems basic
features.

[johnjbarton]

Any site you use Firebug on will show errors. What you say for the net
panel applies equally to the console and script panels: if you load
page with Firebug off, then open Firebug, you will need to reload to
see the Firebug content for these panels.

In 1.4 the phrase "...panel is enable for a domain..." won't apply.
The panel enablement will be independent of the domain.

But your overall concern, that the error count feature of Firebug will
be largely broken, is quite correct.

However, the feature is already broken because Firefox's support of
error reporting is broken. The page of the errors are not identified
by Firefox (nsIConsoleService), I suppose because it was designed
before tab browsing and AJAX. Firebug tries to work around this
problem by comparing the error URLs to URLS for pages it tracks. But
of course if it is not tracking a page, it has nothing to compare to.

With some extra work we could present the total error counts seen by
Firefox and reset this number every time the Firefox location changes.
For simple cases this will be accurate, but if you have multiple tabs
of AJAX sites open, the numbers will be too high. That leaves us with
unhappy users even if we spend time to implement this function.

Either way we can't win, so I'm inclined to put my work towards
features with more upside.

jjb