@Anomie @Esanders Could you shed some light on when the not-supported state is triggered – when browser doesn't support input type=file, correct?

We also require support for HTML5 File API (http://caniuse.com/#feat=fileapi). Unsupported browsers include IE 9 and older, Safari 5 and older, and some older mobile browsers.

@matmarex @Esanders @Jdforrester-WMF Do we have any comparable message on another widget for missing browser support?

In T136149#2333398, @matmarex wrote:

We also require support for HTML5 File API (http://caniuse.com/#feat=fileapi). Unsupported browsers include IE 9 and older, Safari 5 and older, and some older mobile browsers.

I think I am missing something, don't we only check for input type=file in the isSupported method, and not for the File API?

In case the File API and/or drag drop isn't available, but input type=file is, should we degrade to a normal input? Sorry, I don't currently have a way to test this, so asking.

In T136149#2457289, @Prtksxna wrote:

I think I am missing something, don't we only check for input type=file in the isSupported method, and not for the File API?

It checks that an <input type="file"> element can be created and that the element has the files property that is specified by the File API.

In T136149#2457862, @Anomie wrote:

In T136149#2457289, @Prtksxna wrote:

I think I am missing something, don't we only check for input type=file in the isSupported method, and not for the File API?

It checks that an <input type="file"> element can be created and that the element has the files property that is specified by the File API.

Ah, understood. Thanks @Anomie!