Vue-select: Poll: IE 11 Support

[sagalbot]

I'm considering dropping IE11 support to use Proxies for a much improved scoped slot implementation. If IE11 support is important to you - or if it's not, I'd like to know!

Vote with a reaction:

• 👍 to drop IE11
• 👎 to continue IE11 support

---

Related #981

[FloEdelmann]

@sagalbot I'd like to vote :+1: (drop support), but unfortunately many of our customers still use IE11 and can't be convinced to use a modern browser :/

[McKenzieJDan]

Likewise, a number of my clients are using IE11 too.

[erikverbeek]

Sadly also working with clients and customers that still rely on IE11

[WofWca]

If they don't want a modern browser, they wouldn't want a modern vue-select.
Just don't upgrade it.

[erikverbeek]

If they don't want a modern browser, they wouldn't want a modern vue-select.
Just don't upgrade it.

This isn't always the case. Most people using IE either don't understand the difference and just use what is available on their computer. Or they are forced to use IE because their organisation's IT departments don't allow them to install new software.
We still want to give them the best experience possible and being able to use vue-select with it's newest features/bug-fixes, is a far better experience then getting stuck on an old version or switching back to jQuery's select2.

[boriswinner]

Well, if you start using Proxy, you can add a polyfill to the project to continue supporting IE11.

[WofWca]

Well, if you start using Proxy, you can add a polyfill to the project to continue supporting IE11.

Apparently, they're not entirely polyfillable: https://stackoverflow.com/a/45453750/10406353

[sagalbot]

I think I'll look for a way to make it work without proxies. I'd like to see if there are performance downsides to passing the entire VM instance into a slot. Otherwise, I'm just guessing what an implementation might need. Makes more sense to bind the whole VM to a slot, alongside contextual extras (like option when in a loop).