Sounds good. I'll work up a sample page tonight and make a new bug for it.
Thanks! On Aug 6, 12:30 pm, johnjbarton <[email protected]> wrote: > Sounds a bit likehttp://code.google.com/p/fbug/issues/detail?id=2076 > > I'd appreciate this in a bug report so I don't forget about it. > > On Aug 6, 11:11 am, sir_brizz <[email protected]> wrote: > > > I think I finally nailed this down. > > > [script] > > function somefunc() > > { > > var i = 0; > > i = 10; > > i = 20;} > > > [/script] > > > Put a firebug breakpoint on the line with i=20; and then run the > > function. In the console, if you type i and hit enter, you will get a > > response of '20'. > > > Now, with Firebug still paused, switch to another tab and switch back. > > The scope is lost. Typing i and hitting enter will result in nothing > > being returned. > > > On Jun 30, 3:33 pm, sir_brizz <[email protected]> wrote: > > > > Okay. I can't get it to happen with any frequency, seems like > > > occasionally my watch variables will always show as unreferenced and I > > > won't be able to use vars in the console either. It's only happened a > > > few times since I opened this topic. > > > > On Jun 30, 12:55 pm, johnjbarton <[email protected]> wrote: > > > > > Ok, let us know when you find a way to make it happen. The watch > > > > panel requires the Console to be enabled at load time. > > > > > jjb > > > > > On Jun 30, 11:38 am, sir_brizz <[email protected]> wrote: > > > > > > Bah, moments after posting this I tried it again and it seemed to be > > > > > working... WTF? > > > > > > On Jun 30, 12:26 pm, sir_brizz <[email protected]> wrote: > > > > > > > I posted about this several months ago in one of the early 1.4 > > > > > > alphas, > > > > > > though I can't seem to find my post anywhere anymore. > > > > > > > Basically, when you hit a breakpoint, switch to the Console tab, and > > > > > > type any variable name that is in page scope where the breakpoint > > > > > > is, > > > > > > nothing happens. > > > > > > > This also seems to be affecting the watchlist on the Script tab, so > > > > > > both functionality are entirely useless and broken. > > > > > > > The issues currently in 1.4 are problematic now that Firefox 3.5 is > > > > > > actually out :/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
