Incompatible with IE 9 about es6-shim

[ljharb]

Can you be specific as to what's not working? Testling has been unreliable lately.

[cscott]

I can't unfortunately. I believe testling's results in this case but I
think I need to find an ie browser to figure out what's going wrong. I
filed the bug so it wouldn't be forgotten, since I don't think I'm going to
be able to debug this anytime soon. Maybe someone else has more ready
access to IE.
On Oct 12, 2013 12:26 PM, "Jordan Harband" [email protected] wrote:

Can you be specific as to what's not working? Testling has been unreliable
lately.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/156#issuecomment-26200619
.

[cscott]

I found a machine with IE8, and I can confirm that the issues with IE8 are (primarily) with chai, which uses getters and setters and thus doesn't work in IE8 and below. But that doesn't explain the IE9 issues. Hopefully someone with a copy of IE9 handy can check that out.

[ljharb]

This is a more serious issue - IE 8 is an ES3 browser, and the ES6 shim is supposed to work in an ES3 browser that's been ES5 shimmed.

If chai won't work in IE 8, we shouldn't be using chai.

[cscott]

Es6-shim may well work on IE8. We just can't verify that it works because
our test case runner doesn't.
On Oct 16, 2013 7:03 PM, "Jordan Harband" [email protected] wrote:

This is a more serious issue - IE 8 is an ES3 browser, and the ES6 shim is
supposed to work in an ES3 browser that's been ES5 shimmed.

If chai won't work in IE 8, we shouldn't be using chai.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/156#issuecomment-26466668
.

[cscott]

See issue #227. We now work on IE 9/10 when es5-shim is loaded, but they don't support __proto__ (and so Object.getPrototypeOf and Object.setPrototypeOf are not defined on these platforms). IE9/10 also don't support strict mode, so a few of the "null receiver" checks in our test suite are skipped there (see 34b6fec).

[cscott]

I'm going to close this issue; our compatibility situation is much better now and the test suite runs on IE9. (Only one known bug left: #232)