IE11 Compatability

[zslabs]

Hi,
Using IE11 (with an addition of https://cdn.polyfill.io/v2/polyfill.min.js?features=default,matchMedia,fetch,Element.prototype.placeholder,Array.prototype.includes to hopefully grab everything I'd need to for compatibility since I was seeing fetch used) the UI isn't responding correctly; selections are not being added to the list of options; they just disappear. Are there any additional deps I should be using to solidify the browser support?

[jshjohnson]

Hi @zslabs;

Would you be able to send me your config for Choices so I can try and identify the issue?

Thanks

[zslabs]

Hey!
I was testing the default GH pages build (locally) under VirtualBox's modernIE build of IE11.

[jshjohnson]

Hi @zslabs,

This has been resolved as of version 1.1.3. IE doesn't support DocumentFragment.children so I've opted for DocumentFragment.childNodes instead.

Thanks

[zslabs]

Awesome! Thanks so much for jumping on that; can confirm it's working as expected. Appreciate it!

[rstacruz]

I think we still have some IE11 issues. Searching doesn't seem to work. I'll update if I can make a replicable test case.

[caycecollins]

I'm seeing issues with ie11, due to the unsupported es2015 code in the index file:

SCRIPT1002: Syntax error
Choices (249,31)

249        addItemText: (value) => {
250          return `Appuyez sur Entrée pour ajouter <b>"${value}"</b>`;
251        },

[jshjohnson]

Hi @inergy,

Is this on the demo site or your own code?

Thanks

[caycecollins]

On the demo site and I've cloned the repo and can reproduce locally. The index.html file has es2015 code, which I tracked it down to these commits:

• da18bbb
• c2ae162
• 8be12c2

I did a quick refactor using es5 and things started working as expected (after fixing the arrow functions and template literals).

[jshjohnson]

Thanks for the heads up - this should now be resolved with these two commits:

• 31a57a0
• 9bb84df

👍