On 2013/04/17 20:54:58, MarkM wrote:
What actually happens when this is run on the Chrome where
explicit.html fails?
I'm not sure what you're asking about — running explicit.html again?
Running Caja?
If I run explicit.html, then initSES succeeds (at UNSAFE_SPEC_VIOLATION
due to other problems), but the AMD loader test fails because Chrome's
lazily-constructed DOM node prototypes are broken.
This last doesn't matter for Caja because we never manipulate DOM
originating from the SES frame.
https://codereview.appspot.com/8632047/
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
