On Aug 28, 5:39 am, mikerabat <[email protected]> wrote:
> Hi all!
>
> First of all, we love Firebug :)
>
> But there is a nasty bug we are hunting and we are not able to catch
> it.
> Here is the situation:
> * Our server pages are only little stubs, the real content is entirly
> created by javascript
> * We try to cache as much as possible and try to reload the entire
> page (stub + javascript)
> if we detect a verion incompatibility.
> * It works good on our local machines but not on distant servers.
> * The problem is that it's a bit overemphasized and reloads the page
> in the wrong moments.
>
> -> and thats where Firebug should come into the play. The only problem
> is that if a
> page reload occures the complete history in firebug is cleared out and
> restarts, so we don't get
> a chance to look at the real problem.
>
> It would be nice if Firebug has an option to either don't dismiss the
> history or write the complete output to a
> file (actually I would prefere the first one ;)
Firebug 1.5a21 supports "persist" on the console for page reloads. It
copies the console from a web page that is being destroyed into the
console for the new page upon reload. (Every web page has its own
console).
We hope to extend this support to pages that come from the same site
and to the net panel for 1.5.
jjb
>
> Is there already such an option, or where whom could I tell such an
> request?
>
> kind regards
> Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
