Just to follow up. This ended up being my mistake. The scripts I was trying to debug were apparently not available but there were two versions of the same file listed. One under a relative path, the other under the absolute path. Since the relative path scripts took up the whole page and were unable for debugging, I thought there was a problem.
On Aug 20, 6:09 pm, John J Barton <[EMAIL PROTECTED]> wrote: > Not a known problem. There are no bugs with test cases against the > javascript debugging concerning breakpoints. Please attach a test case > to a bug report onhttp://code.google.com/p/fbug/issues/list > > On Aug 20, 2:58 pm, Robert <[EMAIL PROTECTED]> wrote: > > > The Firebug debugger is enabled (also tried enabled for localhost), > > and I can technically set breakpoints. However these breakpoints never > > actually break, and none of the javascript (included or on the page) > > has green line numbers - which I suppose indicates a break point can > > be set there... > > > I haven't spent a long time trying to track down this problem, but I > > can tell you that it is present in FireBug 1.2.0b13 on a brand new > > Firefox 3 profile. I'm including 17 js files in my program (11 local, > > 6 on a hosted CDN) and using them in an embedded script tag. > > > Is this a known issue? Am I the only one who has the problem?... > > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
