Hi Mike. Sounds like the update for the frame is not being tracked by Firebug. You can try to set ERRORS flag on in the tracing window Options tab and look in the log for messages, but I doubt you will see anything. Seems like an omission bug not a component failure bug.
If you open a bug report with a test case I'll take a look. The smaller and more focused the test case the more likely I can find it. http://code.google.com/p/fbug/issues/list jjb On Feb 20, 9:43 am, mshillinger <mshillin...@gmail.com> wrote: > Ran into an issue with FB 1.3.2+ > > My app uses nested framesets > > A top level frameset contains a menu frame and a bottom frameset > > The bottom frameset contains a NavFrame and a ContentPane frame > > The menu will change the bottom frameset using a "parent.frames > [1].location.href='MyFrame.html'" or a "parent.frames > [1].location.replace('MyFrame.html')" > > When the application loads initially - all javascript from all frames > is loaded correctly and I can debug, set breakpoints and step through > code. > > Replacing the bottom frame seems to kill debugging capabilities in > Firebug. > > When the bottom frame is replaced by calling "parent.frames > [1].location.href="SomeFrameset.html"" some of the javascript source > that is loaded (by the contents of the bottom frameset) is NOT > available in the source listing of the "Script" tab. Usually it is the > javascript associated with the 2nd frame in the bottom frameset - but > not always. > > If I change the frame replacement mechanism to use "parent.frames > [1].location.replace('SomeFrameset.html')" the javascript source IS > all loaded into the source list of the "Script" tab, but executable > lines are not marked as executable, while I can set breakpoints in the > code - the breakpoints are ignored (the breakpoint ends up being > named "undefined" or "?") > > If I just load the bottom frameset by itself, everything is loaded and > breakpoints work. > > My application seems to run fine - I just cannot debug it. > > I see the same behavior using the following > > FF 3.0.6/FB 1.3.2 - Ubuntu 8.10 > FF 3.0.6/FB 1.3.3b4 - Windows 2003 > FF 3.0.6/FB 1.4.A12 - Windows 2003 > FF 3.1.b2/FB 1.4.A12 - Windows 2003 > > Also, I created a new FF profile with just Firebug installed to rule > out any plugin conflicts. > > I didn't have any functionality problems with FF3/FB 1.2.x > > Also, I have been using FF2 and FB 1.05 without a problem. > > Working on a test case now - should I submit a bug or is this > something you are aware of? Didn't see anything in the Open Issues > list. > > I can give you a trace if you tell me how to do it. I load the > "tracing enabled" version but was not sure what to trace. > > Thanks > Mike Shillinger --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
