Issue 88132: fix some debugmode issues (Closed)
Description1. you can't use debugmode twice on the same page.
http://code.google.com/p/google-caja/issues/detail?id=637
cajole this in the testbed with debug on:
<script>function f(){}</script>
then try to cajole it again.
the second time fails "___ reused with different debug symbols"
this change fixes that by blithely allowing you to reuse ___ with
different debug symbols. this is not necessarily the right fix,
because two modules coexisting on the same page will stomp on each
other's debugging symbols, but this simple fix reduces frustration
with the testbed in the common case.
2. event handlers can screw up the debug stack and raise a
spurious exception.
http://code.google.com/p/google-caja/issues/detail?id=828
the current code assumes that event handlers are always
top-level entry points, and it clears the debug stack at
every event, but sometimes an event handler can fire
while we're in middle of executing some other js,
and on return from the eventhandler, debugmode tries to
pop from the empty stack, causing an exception.
this change fixes that in two ways:
a. event handlers will not clear the debug stack.
b. debugstack underflow will not raise an exception.
Patch Set 1 #
Total comments: 1
Patch Set 2 : fix some debugmode issues #MessagesTotal messages: 6
|
