I see, so it only persists for refreshing the existing page. That is good to know.
On a side note, given that same page, is there a way for Firebug to track responses from the server side page call that takes place? Currently it doesn't. On Aug 28, 9:49 am, johnjbarton <[email protected]> wrote: > On Aug 28, 8:27 am, sir_brizz <[email protected]> wrote: > > > Can someone try this and tell me their results? > > > On this page:http://digitarald.de/project/fancyupload/3-0/showcase/ > > photoqueue/ > > > if I click Persist and then upload a file and switch to another page, > > the console output does not persist. > > The 1.5a22 console output only persists across reloads. We hope to > extend it to operations that start on one page and end up on another > one connected to the first by the operation (eg click a link). > > Before you ask "why do you just not erase it", I'll repeat what I've > said elsewhere: the operation that causes the console to be empty when > you open a page is *not* erase. Rather it is "create": every page has > its own console. So persistence is implemented by copying elements > from the about-to-be-deleted console to the new one. > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
