Re: should ses work with current Chrome? error from contract.html

On Mon, Mar 23, 2015 at 7:33 PM, Dan Connolly <[email protected]> wrote:
> I get: contract test...failed: TypeError: Function.prototype.apply was
> called on undefined, which is a undefined and not a function
...
> Using Chrome 41.0.2272.89 on Linux


Firefox seems to work fine:


Repair Reports

[+] 2 Fine.

[+] 110 Fine.

[+] 9) Repaired: Non-deletable RegExp statics are a global
communication channel.

[+] 14) Repaired: Date.prototype is a global communication channel.

[+] 15) Repaired: WeakMap.prototype is a global communication channel.

[+] 16) Not repaired: Number.prototype should be a plain object. Safe
spec violation(1).

[+] 17) Not repaired: Boolean.prototype should be a plain object. Safe
spec violation(1).

[+] 18) Not repaired: String.prototype should be a plain object. Safe
spec violation(1).

[+] 19) Not repaired: RegExp.prototype should be a plain object. Safe
spec violation(1).

[+] 63) Not repaired: Strict getter must not box this, but does. Safe
spec violation(1).

Max Severity: Safe spec violation(1).

[+] 2 Fine.

[+] 1) Repaired: WeakMap throws when given some keys.

[+] 132 Deleted.

[+] 3 Frozen harmless.

________________________________

initSES succeeded.

Expected error to test ses.getStack API: [+]Error: Expand me to see stack

Testing ses.getStack with compileExprLater: [+]Error: Expand me to see stack

exprTest...succeeded
moduleTest...succeeded
scriptTest...succeeded
AMD loader test...succeeded
contract test...succeeded

Using Firefox 36.0 on Linux




-- 
Dan Connolly
http://www.madmode.com/