Bug 396568 is fixed in FF3 and anyway deals specifically with multiple inline scripts. So you must have a different problem.
If the URL is changed on reload you won't be able to set breakpoints. If the URL is stable, the fact that the server generates it dynamically is not relevant to Firebug, breakpoints should work. jjb On Sep 21, 8:41 am, Jerry <[EMAIL PROTECTED]> wrote: > The testcase i meant is the one mentioned > inhttps://bugzilla.mozilla.org/show_bug.cgi?id=396568 > . well the problem is the script is dynamically generated in the > server end. Every time the page is refreshed, the little piece of > script too gets downloaded everytime. So the breakpoint also gets lost > as the script is downloaded again from the server. that is why i went > for the debugger statement. I'll raise this as an > issuehttp://code.google.com/p/fbug/issues/list > > -Jerry. > > On Sep 20, 7:34 pm, John J Barton <[EMAIL PROTECTED]> wrote: > > > I don't know what you mean by "the test case". You should not need to > > use 'debugger' statement, just load the page, find the line using the > > Script panel, set a breakpoint, and reload.http://getfirebug.com/js.html > > > But if you use 'debugger' keyword this will work also. If not, please > > open a bug report:http://code.google.com/p/fbug/issues/list > > > jjb > > > On Sep 19, 11:38 pm, Jerry <[EMAIL PROTECTED]> wrote: > > > > Well I am using FF3.0.1 only. And i was using the debugger statement > > > to set the breakpoint as i need to debug from a line ofinline > > >javascriptthat runs onload of a page. As i see the test case do not > > > deal with the debugger statement to set the breakpoint. Will that be > > > an issue? > > > > -Jerry > > > Cognizant > > > > On Sep 15, 3:52 am, John J Barton <[EMAIL PROTECTED]> wrote: > > > > > Which version of Firefox. Sounds like it could be FF2, > > > > see:https://bugzilla.mozilla.org/show_bug.cgi?id=396568 > > > > > On Sep 12, 9:27 pm, Jerry <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > Consider there is a breakpoint/debugger statement on an > > > > >inlinejavascriptthat runs onload of the page. The script debugger > > > > > stops in the place just two lines before the breakpoint/debugger > > > > > statement and highlights it. But the variables in the watch window > > > > > denotes that the script debugger is standing at the exact point where > > > > > the breakpoint was issued. > > > > > There is a bug where in thejavascriptline that is being > > > > > debugged is not highlighted correctly. This happens only in case of > > > > >inlinescripts. I am using Firebug 1.2.1. > > > > > > - Jerry > > > > > Cognizant. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
