add "Disable security" to playground

the chrome/webkit debugger issues are pretty annoying, so I've
added a checkbox to the playground that will make Caja totally
unsafe, but allow the js debugger to work, for both es53 and ses.

[Jasvir, 2012-09-04 22:25:20]

Whelp.  Can you add a test for at least the ses case that only does this
workaround if the bug exists on the browser being tested.

We should roll this back once it's fixed and pushed to Chrome rather than left
in.

[metaweta, 2012-09-04 22:39:49]

On 2012/09/04 22:25:20, Jasvir wrote:
> Whelp.  Can you add a test for at least the ses case that only does this
> workaround if the bug exists on the browser being tested.

How do you test that?  You'd have to know what the debugger's code closes over.

[Mark S. Miller, 2012-09-04 22:51:19]

Yeah, I don't know of a way to test this either.

On Tue, Sep 4, 2012 at 3:39 PM, <metaweta@gmail.com> wrote:

> On 2012/09/04 22:25:20, Jasvir wrote:
>
>> Whelp.  Can you add a test for at least the ses case that only does
>>
> this
>
>> workaround if the bug exists on the browser being tested.
>>
>
> How do you test that?  You'd have to know what the debugger's code
> closes over.
>
>
https://codereview.appspot.**com/6488081/<https://codereview.appspot.com/6488...
>



-- 
    Cheers,
    --MarkM

[Jasvir, 2012-09-04 22:53:35]

Yeah ok - problem only exhibits in the console.

[metaweta, 2012-09-04 23:05:14]

lgtm

[felix8a, 2012-09-05 00:30:49]

@r5035