Uppy: Drop IE 10-11 support?

[arturi]

For example, for this: https://github.com/feross/drag-drop/commit/b832c66716d9a7e1dd3e4f0155dfb9ed8c964a5a. But also to simplify testing, use more modern JS features and less polyfills.

[kvz]

I'd be fine with this

[ghost]

This would also allow the DragDrop plugin to be updated to set the files of the target input thanks to https://github.com/feross/drag-drop/commit/1ea971c693d81fd575b06496a95975066146cbba (context here).

[goto-bus-stop]

IE11 still has a pretty sizeable userbase (3ish% according to caniuse). IMO dropping it from the default support set is OK as long as everything we use is polyfillable.

[hpvd]

Since uppy is a perfect tool to be used also in the field of B2B (and some industries are really slow on updating their environment) I would vote strongly for keeping support as long as possible.

Maybe one indicator could be, how the tools connected with in uppy (Dropbox, google drive etc) handles this.
imho: As long as some of them do support IE10&11 in a good way, uppy should do this too.

Other wise uppy would be "weakest" tool in this chain...

[ghost]

To clarify, are we speaking about dropping support for IE for all of uppy, or just the DragDrop plugin?

[goto-bus-stop]

All of it, I believe. I broadly agree with @hpvd, but think that we could drop default support if we recommend a set of polyfills that will make it work. I think we should keep IE in tests with polyfills in that case.

[goto-bus-stop]

Let's also do this before 1.0 then? Else we'll have to wait for 2.0 :)

[arturi]

Yes, let’s drop Promise and Fetch built-ins and recommend them as polyfills soon. Not sure about Array.from and all those though.