Firebug 1.4 - Can't refresh cache without disabling Firebug

[lieut_data]

Recently upgraded to Firebug 1.4, and I've been totally unable to use
Firebug to its full capacity. In fact, I'm really finding web
development in general very frustrating without the features I've come
to love! (I love Firebug :)). Anyway, to the specific problem at hand:

With Firebug 1.3 and below, reloading the page would reload Firebug
*and* download a new copy of the source being worked on. This no
longer appears to be the case -- as long as Firebug is opened, the old
cache remains. In order to test new changes, I'm now forced to close /
suspend Firebug, reload the page, and then re-enable firebug. Of
course, then, I miss the AJAX requests fired on page loading, so I
have to refresh *again* to get those.

On another note, the on/off suspend/activate behaviour is confusing.
For one, the right-most button is now "turn off Firebug", whereas
before it was "hide firebug but keep on doing all the firebug
goodness". I rarely want to disable Firebug once I've activated it for
a specific page. But I frequently want to make better use of my
screen's real-estate. Plus, now Firebug hides and immediately
reappears whenever I reload a page. This is really annoying, as I
don't see why Firebug should have to completely disappear when it
knows it's about to reappear.

[johnjbarton]

On Jul 24, 3:07 pm, lieut_data <jesse.hal...@gmail.com> wrote:
> Recently upgraded to Firebug 1.4, and I've been totally unable to use
> Firebug to its full capacity. In fact, I'm really finding web
> development in general very frustrating without the features I've come
> to love! (I love Firebug :)). Anyway, to the specific problem at hand:
>
> With Firebug 1.3 and below, reloading the page would reload Firebug
> *and* download a new copy of the source being worked on. This no
> longer appears to be the case -- as long as Firebug is opened, the old

As far as we know, Firebug is now working correctly and before it was
working incorrectly. Firebug should be showing you the js from the
web page you are looking at, not the js from the server at a different
time.

> cache remains. In order to test new changes, I'm now forced to close /

Don't push the "Off" button on pages you want to debug.

> suspend Firebug, reload the page, and then re-enable firebug. Of
> course, then, I miss the AJAX requests fired on page loading, so I
> have to refresh *again* to get those.

You can just use Ctrl-F5 to reload with out cache.

>
> On another note, the on/off suspend/activate behaviour is confusing.
> For one, the right-most button is now "turn off Firebug", whereas
> before it was "hide firebug but keep on doing all the firebug
> goodness". I rarely want to disable Firebug once I've activated it for
> a specific page. But I frequently want to make better use of my

The [_] button minimizes firebug; so does the status bar icon; so does
F12.

> screen's real-estate. Plus, now Firebug hides and immediately
> reappears whenever I reload a page. This is really annoying, as I
> don't see why Firebug should have to completely disappear when it
> knows it's about to reappear.

It does not know that.

jjb

[Steven Roussey]

> > screen's real-estate. Plus, now Firebug hides and immediately
> > reappears whenever I reload a page. This is really annoying, as I
> > don't see why Firebug should have to completely disappear when it
> > knows it's about to reappear.
>
> It does not know that.

I wonder if there is something Mozilla can do in Firefox 3.6 to help
with that...

[johnjbarton]

I think we can tell in some cases. But I don't know if I can figure
out how to stop the close/open. Its complicated stuff.

jjb

[lieut_data]

On Jul 24, 6:30 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> On Jul 24, 3:07 pm, lieut_data <jesse.hal...@gmail.com> wrote:
>
> > With Firebug 1.3 and below, reloading the page would reload Firebug
> > *and* download a new copy of the source being worked on. This no
> > longer appears to be the case -- as long as Firebug is opened, the old
>
> As far as we know, Firebug is now working correctly and before it was
> working incorrectly.  Firebug should be showing you the js from the
> web page you are looking at, not the js from the server at a different
> time.

It's always fun when a bug becomes a feature :) -- Ctrl-Shift-R now
does what I had become accustomed to Ctrl-R doing.

Thanks for pointing this out!

> > On another note, the on/off suspend/activate behaviour is confusing.
> > For one, the right-most button is now "turn off Firebug", whereas
> > before it was "hide firebug but keep on doing all the firebug
> > goodness". I rarely want to disable Firebug once I've activated it for
> > a specific page. But I frequently want to make better use of my
>
> The [_] button minimizes firebug; so does the status bar icon; so does
> F12.

F12 fits my bill -- thanks again!

> > screen's real-estate. Plus, now Firebug hides and immediately
> > reappears whenever I reload a page. This is really annoying, as I
> > don't see why Firebug should have to completely disappear when it
> > knows it's about to reappear.
>
> It does not know that.

Fair enough -- I guess, again, I was used to the old behaviour where
the Firebug was always on for the page I was working on, so re-loading
wouldn't hide and re-show the page.

[johnjbarton]

On Jul 27, 11:43 am, lieut_data <jesse.hal...@gmail.com> wrote:
...

> > > screen's real-estate. Plus, now Firebug hides and immediately
> > > reappears whenever I reload a page. This is really annoying, as I
> > > don't see why Firebug should have to completely disappear when it
> > > knows it's about to reappear.
>
> > It does not know that.
>
> Fair enough -- I guess, again, I was used to the old behaviour where
> the Firebug was always on for the page I was working on, so re-loading
> wouldn't hide and re-show the page.

Sorry it did not work that way. There is no such thing as "on for the
page". Firebug works on windows. When the window is destroyed, what is
Firebug to do? It remembers the URL of the window and it can notice
when a window appears with that URL. Then it can begin processing this
"new page". Since the window is destroyed on reload, there isn't any
old page any more. If it looked like Firebug was "always on for the
page' it was just an illusion.

But we can "not close" Firebug when the new URL is the same as the old
URL. I have that working in 1.5 and we hope to put it in 1.4.1. My
only concern is discoveriing cases where Firebug should close but does
not.

jjb

jjb

[Nicolas Hatier]

Is it simply possible that v1.3 appeared on the page earlier in the page loading process, making it look like it never "closed", and didn't trigger the page's onresize event?

NH

jjb