Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try fixing IE #1818

Merged
merged 3 commits into from
Feb 12, 2016
Merged

Try fixing IE #1818

merged 3 commits into from
Feb 12, 2016

Conversation

dignifiedquire
Copy link
Member

No description provided.

var parser = new DOMParser()
var doc = parser.parseFromString('<test></test>', 'application/xml')
expect(stringify(doc)).to.be.eql('<test></test>')
if (DOMParser) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will throw if DOMParser is not defined so this check doesn't work. You need to check for typeof being !== 'undefined'.

@dignifiedquire
Copy link
Member Author

Thanks @mgol! any ideas on why IE 6 completely refuses to connect?

@dignifiedquire dignifiedquire mentioned this pull request Feb 1, 2016
3 tasks
@mgol
Copy link
Contributor

mgol commented Feb 3, 2016

It seems mocha is broken in IE<9? Could you try to update it? Also, it seems they still support IE8 but I'm not sure if they care about IE 6 & 7... What can we do if that's the case?

@dignifiedquire
Copy link
Member Author

@mgol hmm, I will update and we will have to see, I'm already including polyfills for older browsers so that might be enough to get things working with mocha. But I expect to see a big drop in library support for IE 6 - 9 now that Microsoft officially dropped them all from their support list.

@mgol
Copy link
Contributor

mgol commented Feb 3, 2016

But I expect to see a big drop in library support for IE 6 - 9 now that Microsoft officially dropped them all from their support list.

Probable but considering that Angular 1 & 2 & Ember still support IE 9, at least IE 9+ will be necessary to support by Karma for some time. Unfortunately, test runners need to be a little more conservative in dropping older browsers than libraries/frameworks that are using them. :)

@dignifiedquire
Copy link
Member Author

Unfortunately, test runners need to be a little more conservative in dropping older browsers than libraries/frameworks that are using them. :)

Yeah I know, that's why I'm trying to fix this. Just saying that libraries like mocha might not bother to do so.

@PixnBits
Copy link

PixnBits commented Feb 3, 2016

FWIW Vista is IE9 and isn't EoL until 2017
Some embedded Windows OSes still live and are IE8 :'(
https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer

@mgol
Copy link
Contributor

mgol commented Feb 3, 2016

This is a little OT but I've made a table compiled from https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer & https://support.microsoft.com/en-us/gp/lifeselectindex:

Desktop:

  • IE 9: 2017-04-11 (Windows Vista)
  • IE 11:
    • 2023-01-10 (Windows 8.1)
    • ????-??-?? (Windows 10)

Others:

  • IE 7: 2016-04-12 (Windows Embedded for Point of Service (WEPOS))
  • IE 8:
    • 2017-01-10* (Windows Thin PC (Embedded))
    • 2019-01-08 (Windows Embedded Standard 2009)
    • 2019-04-09 (Windows Embedded POSReady 2009)
  • IE 9: 2020-01-14 (Windows Server 2008)
  • IE 10:
    • 2023-01-10 (Windows Server 2012)
    • 2023-07-11 (Windows Embedded 8 Standard)
  • IE 11:
    • 2020-01-14 (Windows Server 2008 R2)
    • 2020-10-13 (Windows Embedded Standard 7)
    • 2021-10-12 (Windows Embedded POSReady 7)
    • 2021-10-12* (Windows Thin PC (Embedded))
    • 2023-01-10 (Windows Server 2012 R2)
    • 2023-01-10 (Windows Embedded 8 + Windows 8.1 Industry Update)
    • ????-??-?? (Windows Server 2016)

* Beginning January 10, 2017, only Internet Explorer 11 will be supported on Windows Thin PC. In order to continue to receive Internet Explorer 8 updates after January 12, 2016, please contact your Microsoft Account Team.

@dignifiedquire
Copy link
Member Author

thanks @mgol so the only one that is fully unsupported right now is IE 6 as far as I understand.

If I can get these tests to pass we should be back with support for 7 and above would that be enough for your use cases?

@mgol
Copy link
Contributor

mgol commented Feb 3, 2016

@dignifiedquire Sizzle (jQuery selector engine) still supports IE 6 but we'll be dropping at least this version soon so if we made Karma work in IE 7+ we'd be happy. :)

@dignifiedquire
Copy link
Member Author

@mgol I have things passing in IE7 on my local VM saucelabs is still a bit whiny but we'll get there, mind taking this for a spin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants