window.onerror available in Chrome 10

[Igor Minar]

window.onerror is now available in Chrome 10. I know that lack of the global error handler was giving jstd a hard time.

does anything need to be done in JSTD to take advantage of this fix or will things "just get better" on their own.

Reference: http://code.google.com/p/chromium/issues/detail?id=7771#c29

/i

[Cory Smith]

Should just work (the signature is the same as ff and ie). Try loading
a file with a syntax error, and it should be reported.

-c

> --
> You received this message because you are subscribed to the Google Groups
> "JsTestDriver" group.
> To post to this group, send email to js-test...@googlegroups.com.
> To unsubscribe from this group, send email to
> js-test-drive...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/js-test-driver?hl=en.
>

[Igor Minar]

It took a lot of digging to find an old chrome version, but I can confirm that the issue is now fixed:

Total 6 tests (Passed: 6; Fails: 0; Errors: 0) (51.00 ms)

  Chrome 10.0.648.151 : Run 3 tests (Passed: 2; Fails: 0; Errors 1) (51.00 ms)

    error loading file: /test/test/widgetsSpec.js:868: Uncaught SyntaxError: Unexpected token var

  Chrome 11.0.686.0 Mac OS: Run 3 tests (Passed: 2; Fails: 0; Errors 1) (6.00 ms)

    error loading file: /test/test/widgetsSpec.js:868: Uncaught SyntaxError: Unexpected token var

  Chrome 5.0.329.0 Mac OS: Run 2 tests (Passed: 2; Fails: 0; Errors 0) (8.00 ms)

no that the last chrome slave didn't report any errors while all others did.

/i

[Cory Smith]

Awesome. Thanks for testing this!

-c