I'm looking into an alternative model for these kinds of cases. The "break on next except not on mouse over not on mouse out not on setTimeout noto setInterval" seems like problem.
jjb On Nov 4, 10:57 am, Nicolas Hatier <[email protected]> wrote: > An option to ignore mouseover/move/out events for Break On Next would be > very helpful too. > > NH > > Prefontim wrote: > > If i set break on next on foo.html, but have a timer in bar.html, the > > the break on next will stop on the timer in bar.html, so this is a > > bug. > > > It would be nice to also have a 'ignore timers' feature, so it won't > > keep stopping on these timers. > > > On Nov 4, 12:12 pm, John J Barton <[email protected]> wrote: > > >> On Nov 4, 9:05 am, Les <[email protected]> wrote: > > >>> I can provide a test showing this behavior: > > >>> 1. Go here:http://www.officemax.com/ > >>> 2. Click Break on Next > >>> 3. You will see that almost immediately the debugger stop in a > >>> function function br_indomain_loop() > > >>> This function has a timer that wakes up some code every 1000ms, so it > >>> will break inside this loop. > > >>> There should be a way for Break on Next to ignore timers. > > >> Ok, but this is not what I understood from Prefontim. I mean, "break > >> on next" worked as designed, but of course you want another design I > >> understand. > >> jjb > > > -- > > > 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 > > athttp://groups.google.com/group/firebug?hl=en. > > -- 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.
