Sebastian, you haven't addressed my core question, which doesn't require looking at *any* code: in general, what makes a line of code "breakable" (in any debugger, not just Firebug)? Why is some code executable from the browser's point of view but not from the debugger's?
@Mahks Doma: No, there are no iframes in that page, and no Ajax either. Also no linked libraries like jQuery or whatever -- I write almost all my own code from scratch. Some of the JS values were set via PHP, but that shouldn't matter; that's history by the time the debugger sees it. It is complex code, with nested functions, objects, conditionals, and branching logic, and more than one JS file linked into the html page. Only one of the JS files shows the breakpoints problem, but that code works well in the page and throws no errors. My intuition says debugger "breakability" may have something to do with scope, or code branching... but I just don't see the pattern. *Somebody* must have written the code in Firebug that decides (not always correctly) which line numbers to turn green -- and that person must know what the logic is. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/CAMoMLKh7bAg3SirXcbKjbZW8MQLSTRancAAuCcCB8%2B4_5w8JhQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
