On Thursday, February 19, 2015 at 3:41:07 PM UTC+1, San wrote: > > > On Thu, Feb 19, 2015 at 3:45 AM, Sebastian Zartner <[email protected] > <javascript:>> wrote: > >> Can you post the link to that thread? > > > ​Sorry, not easily, because I'm reading this in gmail. But I'm referring > to the thread entitled "firebug 2.0.8 stops at no breakpoints in firefox > 35.0.1 on Mac or PC" that was started (by somebody else) six days ago on > February 13. >
Found it. https://groups.google.com/d/topic/firebug/fS_Szmt6QZE/discussion. The first person describes another issue than you. You say that the stepping functionality doesn't work when you hit a breakpoint, while he says that he can't set any breakpoints and just sees a throbber where the breakpoint should be. I am using Firefox 35.0.1 + Firebug 2.0.8 on Win7 and I did not encounter >> this issue so far. >> > > Interesting. Are you running Firebug in a separate window? I've found the > breakpoints problem in that case are more reproducible. > Yes, I tried it while Firebug was detached on several websites and it did not happen to me. The debugger buttons were always activated once the script execution was halted. My steps on one of the pages: 1. Opened Firebug on https://getfirebug.com/tests/manual/console/joes-original/test.html 2. Enabled and switched to the *Script* panel 3. Set a breakpoint at line 23 of test.html (console.log("This is a call to log with multiple arguments.", document.body, 42);) 4. Clicked the log button on the page => The execution halted at line 23 and the debugger buttons were active. > A test case with steps to reproduce... >> > > ...is something I'm not familiar with and don't have time for. A test case is what I did above. I.e. writing down the steps you did on a specific page where the problem can be reproduced. See https://getfirebug.com/wiki/index.php/Creating_a_Test_Case for more info. If you don't have time to create a test case, you should follow the quick-fix steps described on the first aid page <https://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#The_quickest_way_to_stop_having_the_problem>. Though if you want the bug to be fixed, you should follow the instructions to help the team understand the problem <https://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#To_understand_the_problem_so_it_can_be_fixed> . When, years ago, I was a volunteer beta tester for a few major software > products (programs that everyone is familiar with) nobody ever asked me to > use a standard format or put together test cases. I just reported the > problems, and their teams followed up from there. Then I wonder how they could fix issues, which were not obvious. Generally a programmer needs to be able to reproduce a bug in order to fix it. Sebastian -- 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/0f7a78b8-490b-4241-bcf3-394a113d7e3a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
