Maybe it will help if I explain that when you reload a web page (I guess that is what you mean by 'refresh'), the window object in the current page and all of the page contents are deleted by Firefox. These are all gone as are the compilation results that contain the breakpoints. Then a new page is created with a new window object and the javascript is all recompiled. Then firebug needs to reset the breakpoints. It does this by comparing the URLs of compilation results to a table of breakpoints it has stored based on user actions. This table is [url, linenumber]. When it can, Firebug resets the breakpoints for any matching [url,linenumber] it finds.
>From this you can notice some consequences. If the url changes or does not match for some reason or the line number changes or Firebug encounters a problem anywhere in the processing of a new page, then the breakpoint will not be set. Unfortunately there are lots of ways for this to happen so only by creating a test case can I tell you what happened in you case. jjb On Mar 24, 8:18 am, Lee Merrill <[email protected]> wrote: > Just FYI, I should mention that the first breakpoint set doesn't bring > up the debugger when the browser is refreshed. > > Now another developer duplicated this problem, and also discovered > that setting a breakpoint on a Javascript function that runs when you > click a button works (this works for me too), only refreshing the > browser doesn't seem to catch breakpoints. > > Lee --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
