This is something I've thought about since day one, but I figured there was nothing you can do about this type of "vulnerability". But maybe with the new ES5 sandboxing, there's something that can be done about this? Currently, using server-side cajoling, visiting someone's sandboxed app within my application causes the whole browser to BSOD, probably making it look like my application itself is somehow broken. Could client-side caja somehow let just the sandboxed code timeout, and keep my application running normally afterwards?
-- --- 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.
