I can't really comment to the headers. I'm not that knowledgable about
them. However, with firebug disabled I very, very rarely see Firefox
hang onto old cache since I updated to 3.0.x.


On Sep 25, 11:29 am, John J Barton <[EMAIL PROTECTED]>
wrote:
> There is some other condition which causes this I suppose. I edit js
> files all day with the script panel open and breakpoints set and I
> never see this. Other folks have said they see it. Perhaps it has to
> do with cache settings or other HTTP headers?  My debugging server
> ignores all the http headers.
>
> jjb
>
> On Sep 25, 5:04 am, Andrew Powell <[EMAIL PROTECTED]> wrote:
>
> > Hello all,
>
> > First time/long time. There is a particular problem with Firebug which
> > is a huge PITA and has been persistent for a long time. I've been
> > patient and waited a few versions to see if it was going to be
> > resolved, but has not yet been.
>
> > Frequently, when I am debugging a website's javascript [locally], I'll
> > modify the contents of the script file and refresh the browser to load
> > the newly modified script. Frequently, the script will not be
> > refreshed and Firebug will continue to display and execute the
> > previous version of the script. Now, this may or may not be a core
> > mozilla issue. However, this happens only when; Firebug's Script
> > display window is open and I have been walking through script -or- if
> > I have any breakpoints set. If either of those two conditions are
> > false I never experience the issue.
>
> > Firebug 1.2.1
> > Firefox 3.0.2
>
> > Thanks!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to