Two rather irritating things...

[Zaph]

Hey,

as a webdeveloper I love Firebug, but there are two things that really
bug me out.

The first one is that the Firebug panel opens spontaneously when I
browse to an arbitrary site where I have once (I assume) used Firebug.
This bug has been going on for several versions and I haven't been
able to detect any form of predictability (even non-cached pages can
cause it).

The second, unrelated to the above, is 'Break on All Errors' which
seems to have a mind of it's own. When I have the panel hidden, it
sometimes triggers, and sometimes doesn't. This one is as new as the
'Break on All Errors' option, as far as I know.

Bottom line - I'm getting pretty fed up with Firebug popping up out of
nowhere when I'm just merrily clicking away and didn't ask for it.

I really hope there's a way to get around this, because I'd hate to
deinstall it.

Peter

--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com.
To unsubscribe from this group, send email to firebug+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[John J Barton]

On Apr 23, 3:53 pm, Zaph <pe...@zaph.nl> wrote:
> Hey,
>
> as a webdeveloper I love Firebug, but there are two things that really
> bug me out.

You need to tell us which version of Firebug.

>
> The first one is that the Firebug panel opens spontaneously when I
> browse to an arbitrary site where I have once (I assume) used Firebug.
> This bug has been going on for several versions and I haven't been
> able to detect any form of predictability (even non-cached pages can
> cause it).

You should do two things:
Firebug Icon Menu > Options > Reset All
Right Click Firebug Status Bar Icon > Clear Activations.

Then read
http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-15/

>
> The second, unrelated to the above, is 'Break on All Errors' which
> seems to have a mind of it's own. When I have the panel hidden, it
> sometimes triggers, and sometimes doesn't. This one is as new as the
> 'Break on All Errors' option, as far as I know.

Sound like you are using 1.4.

1.5 has better support for break on error, I recommend break on
specific errors rather than All.
1.6 has better support for break on all errors, allows you to break
once then skip in future.

jjb

[Zaph]

Thanks for your quick resonse!

>
> You need to tell us which version of Firebug.
>

Yeah, that was dumb - it gets updated whenever Firefox finds a new
version, and I'm using 1.5.3 at the moment.

>
> Then readhttp://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-...
>

I never realised that the icon has two statuses - coloured and grayed.
I open and close it with F12, and it turns out that F12 only only
minimizes it instead of disabling it.

>
> 1.5 has better support for break on error, I recommend break on
> specific errors rather than All.

That's not very productive when you're programming complex javascript
applications... ;-)

> 1.6 has better support for break on all errors, allows you to break
> once then skip in future.
>

Well, what happens is I'm working on a website with Firebug active,
and when I need a short break I close it with F12, visit some
newssites and forums, and then suddenly it pops up because there's a
javascript error.

[John J Barton]

On Apr 24, 3:26 am, Zaph <pe...@zaph.nl> wrote:
> Thanks for your quick resonse!
>
>
>
> > You need to tell us which version of Firebug.
>
> Yeah, that was dumb - it gets updated whenever Firefox finds a new
> version, and I'm using 1.5.3 at the moment.
>
>
>
> > Then readhttp://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-...
>
> I never realised that the icon has two statuses - coloured and grayed.
> I open and close it with F12, and it turns out that F12 only only
> minimizes it instead of disabling it.
>
>
>
> > 1.5 has better support for break on error, I recommend break on
> > specific errors rather than All.
>
> That's not very productive when you're programming complex javascript
> applications... ;-)

By breaking on specific errors you can concentrate on fixing one
without another one distracting you in the process.

>
> > 1.6 has better support for break on all errors, allows you to break
> > once then skip in future.
>
> Well, what happens is I'm working on a website with Firebug active,
> and when I need a short break I close it with F12, visit some
> newssites and forums, and then suddenly it pops up because there's a
> javascript error.

You will need to decide. If you want Firebug to pop up when an error
occurs, then set Break on All Errors and leave Firebug active. If you
don't want Firebug to pop up, then either click the Break On All
Errors off or click Firebug Off. We are working on reading your mind
to know when you want the error notification, but these feature won't
be available soon ;-)

jjb

[Zaph]

> By breaking on specific errors you can concentrate on fixing one
> without another one distracting you in the process.
>

Yeah, I know how debugging works... ;-)

> We are working on reading your mind
> to know when you want the error notification, but these feature won't
> be available soon ;-)
>

Then stop wasting time here and get on with it! ;-)

Seriously, it's all caused by my assumption that closing Firebug with
F12 disabled it as well, which would make more sense in my opnion, but
is sadly not the case.

Anyway - it's clear to me, and I know how to deal with it. Thank you
for your time!

Peter

[John J Barton]

On Apr 24, 10:23 am, Zaph <pe...@zaph.nl> wrote:
> > By breaking on specific errors you can concentrate on fixing one
> > without another one distracting you in the process.
>
> Yeah, I know how debugging works... ;-)
>
> > We are working on reading your mind
> > to know when you want the error notification, but these feature won't
> > be available soon ;-)
>
> Then stop wasting time here and get on with it! ;-)
>
>  Seriously, it's all caused by my assumption that closing Firebug with
> F12 disabled it as well, which would make more sense in my opnion, but
> is sadly not the case.

Well we call it "minimizing Firebug" to remind us that its still
active.

We had a lot of discussion about this issue a year ago. Making the
main icon toggle "on, minimize, unminimize, minimize" works very well
for devs that need to pop firebug in and out. It makes turning Firebug
"off" not a toggle: you have to work harder and that acts a little
like a confirmation that you really want it off.

jjb