Trying this in a new Firefox profile on Windows 7 with the same Firefox and 
Firebug versions as you I first couldn't see this problem, but after some 
switching between tabs and restarting the browser it happened to me, too. 
Though a simple page reload could always fix those issues.

While testing this I ran into another (known) issue 
<https://github.com/firebug/firebug/issues/7867>, which is a throbber shown 
forever instead of the breakpoint.

Note that Firebug 3 will integrate into the built-in DevTools, which 
obviously don't have this issue. As focus lies on Firebug 3 development, I 
also doubt that this bug will still be fixed for Firebug 2. So I suggest to 
give the built-in Firefox DevTools a try. (Note: Their debugger can be 
opened via Ctrl+Shift+S.)

Sebastian


On Sunday, April 17, 2016 at 9:08:54 AM UTC+2, Jonathan Mills wrote:
>
> I've been trying to use firebug (2.0.16 / FF 45.0.2 / Windows 10), but I 
> have hit a problem.  Code snippet attached, but relevant bits here.
>
> function start() {
>   setTimeout(monitorOutstanding, 1000) 
> }
>
> function monitorOutstanding() { 
>
>   // The next line is "Line B" 
>   var nextTimeout=1000 
>
>   // The next line is "Line A" 
>   if (nextTimeout !== 0) setTimeout('monitorOutstanding()',nextTimeout) 
> }
>
>
>  ... If I set the breakpoint on "Line A" (the if statement), that is 
> marked ok, and I reload the page and the breakpoint is hit as expected.
>
> But if I try and set another breakpoint - say "Line B", the red breakpoint 
> glyph does not appear.
>
> If I click on the red glyph on Line A, it vanishes.
>
> If I then click on Line B again to establish the breakpoint - a breakpoint 
> re-appears -- but on Line A!
>
> I have tried creating a new profile and only loading Firebug; it still 
> fails.  Any ideas? 
>
> I did wonder about reporting it as a bug, but 
> https://code.google.com/archive/p/fbug/wikis/Issues.wiki says "report 
> firebug 2 problems here" and takes me to a page where I can see issues but 
> not report them.
>
> I have had to debug the problems which led to this with Chrome, which 
> isn't as pleasant an experience. 
>
> Jonathan
>
>
>
>

-- 
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 https://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/6540b2c3-13fa-4aaa-9f80-d47c6d58f87e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to