Each context has a set of panels; each context corresponds to a page. I'd start by tracing with DBG_WINDOWS to understand the order of events: does the destroyContext come before the initContext for new page or not? My guess is yes. So then you need to decide: how to prevent destroyContext only in cases where I want to retain the panel?
hth, jjb On Sep 24, 1:23 pm, Alex <[EMAIL PROTECTED]> wrote: > Thanks for the quick reply! > > In fact, I want the "easy" feature: One panel that doesn't reload when > a new page is loaded into the current browser tab. Let's say I want to > protocol the text content of all title tags of all pages loaded into > the browser tab. Of course, I could just remember all title tags and > write them to the fresh panel, which is (obviously) not what I want to > do. So I guess the question is: How do I communicate to tabWatcher > that I do not want to delete the panel? How can I keep a panel over a > page reload? > > History-dependent panels are pretty appealing, too. But the easy > version would do fine for now; in particular, given that you plan to > drop tabWatcher. > > Again, I'd like to thank you for your reply. Have a good day, > > Alex > > On Sep 24, 9:07 pm, John J Barton <[EMAIL PROTECTED]> wrote: > > > It would be easy to for the console to show errors and warning for > > several pages, as long as by "several pages" you mean "all pages" ;-) > > > What you probably want is "when this page POSTs and gets a reply, put > > the new page errors in the same console as I have now". There are > > lots of folks who want this feature. > > > The problem is "how can Firebug determine that a page load event is > > connected in some way to a previous page?" > > > Here is one idea: when tabWatcher sees a new page it could look up the > > URL in the Net panel list of previous requests for every context. If > > one of the contexts did a request that matches, set the context of the > > new load to the match and issue "loadedContext". You also have to > > handle redirects. > > > If you succeed at that part the rest is simple. Well, I guess it > > depends on whether the new page events come before or after the call > > to destroy the old page. > > > By the way our plan is to eventually drop tabWatcher once we get a new > > API from Firefox. But that depends > > onhttps://bugzilla.mozilla.org/show_bug.cgi?id=342715 > > and it could be a ways off. > > > jjb > > > On Sep 24, 11:39 am, Alex <[EMAIL PROTECTED]> wrote: > > > > Hello everybody and thanks a lot for Firebug! > > > > My question is the following: Is there a simple way (internal option, > > > say), to build persistent panels, ie. panels that can gather > > > information over several pages / page reloads? As an example, the > > > Console panel could then optionally show errors and warnings from > > > several pages. > > > > I am building an extension for Firebug and am very much interested in > > > such a feature. If there is no easy option (which is what I suppose), > > > I would be very glad to get some expert advise (the more detailed the > > > better) on how an implementation of such a persistent panel should > > > look like (passing/gathering context information, avoiding the > > > destruction of a panel, etc). > > > > I really hope someone finds the time to reply to this. Thanks a lot in > > > advance! Your help is very appreciated. > > > > Best regards, > > > > Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
