On Apr 22, 3:11 pm, Steven Roussey <[email protected]> wrote:
> As far as implement, I was referencing onError knowing the window that
> the error was on like onDebug does. Is there no onException that is
> separate from onError/onDebug? I hope the Mozilla people take your
> feature requests as high priority...
Exceptions come through onError() with properties that allow you to
decide that they are exceptions.
Mozilla people do give Firebug-related feature requests high priority.
The problem here is that no Mozilla person is in charge of the code
involved in onError().
>
> Back to the bug, do you know how I could trigger it without Firebug? I
Using my build of FF3.5 I am able to see that Flash plugin is
evaluating JS and an error does come in "movieElement is undefined".
Then the Firebug Break on Error code is invoked (I can't be 100% sure
since I am looking at C++ stack). Then the Firefox event loop is
entered.
So Firebug is waiting for CPU time to update its display. Firefox is
waiting for a native event to fire. EOF.
My guess is that Flash has somehow disabled the Firefox event loop
since it wants to be in control while JS evaluation continues. It
does not expect the JS evaluation to call back into Firefox UI (which
is what Firebug is doing).
I'll ask for help from the mozilla folks.
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 at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
