RF 4.5.0.Beta2 rich:fileUpload does not work in IE9

[thinkdev]

Moving from RF4.3 to RF4.5, I noticed that the rich:fileUpload component stopped working for IE9.  IE9 does not support the File API, and while I see that some of the JavaScript for the file upload control does try to do a bit of feature detection, it still winds up throwing some exceptions (file.name is undefined and then the code tries to perform .match on undefined).

Is there any plan on supporting browsers that do not implement the File API?  The file upload control in RF4.3.7 worked for just about every browser I tried it on, though I can see that the RF4.5.0 file upload control is a lot nicer (thanks to File API).  Is this something I should file a defect about?

Edit: At the very least, maybe fileupload.js could do something like if(window.File && window.FileReader ...) and error out nicely as opposed to dying.

[bluez974]

Hello, can you tell me which jsf implementation do you use please ? Because  i wasn't able to make this component work properly under RF 4.3.7 and Firefox . I wonder if it is not because of MyFaces 2.2.4.

Have a look at this : http://stackoverflow.com/a/21157340

[michpetrov]

The 4.3.x fileUpload does not work with Servlet 3.0. I.e. the "problem" is the server, not your JSF implementation.

[thinkdev]

I was using JSF 2.1.29 (Mojarra) on Tomcat 7.

I'm left in a bit of a sticky situation -- while I would like to use the latest RF and get all of the new goodness in the latest build of RF, the browser compatibility requirements for my project are such that I will have to downgrade back to 4.3.  RF4.5 does fix a lot of issues and is really nice, though.

[extremo]

+1

[thinkdev]

It isn't going to happen.  I filed a JIRA defect ([RF-13843] rich:fileUpload should use feature detection for File API - JBoss Issue Tracker) to at least gracefully error out if the File API was not supported by the browser.  (Just about everything out there does support it aside from IE9 and a few mobile browsers.)  I figure that feature detection of these things is an easy best practice.  In any case, they revised the target browser list for RF4.5 and eliminated IE9 support.