You can try this:
Firebug > Script > [||] (Break on next)
you should land in the JS debugger on the next clock call.
Open the command line and try to re-assign the clock update method. So
eg
setTimeout(foo, 1000); // annoy papayasoft every second
then
foo = new Function("return;");
jjb
On Aug 2, 10:36 pm, papayasoft <[email protected]> wrote:
> On a page I am debugging, there is a javascript clock. An onload event
> starts a timer using setTimeout(), on each fire of the timer, the
> content of an element #clock is modified. Page loads fine, timer and
> clock runs as expected.
>
> But if I Inspect Element on some other element of the page
> #someElement, (so now I am within the HTML tab) every firing of the
> timer pulls the focus from #someElement back to #clock.
>
> Is this a bug?
>
> If not, is there some way to use the debugger to disable a segment of
> javascript code that has been loaded? My workaround so far has been to
> simply remove the #clock element from the DOM. But since the timer is
> still running and attempts to update the content of the #clock
> element, we get an error on every timer firing. Clogs the Console,
> probably eats memory, etc.
>
> Any ideas?
>
> Thanks and cheers!
--
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.
