Uploader's underlying upload manager, SWFUpload has regressed in Firefox 3.5. As a result, it is throwing exceptions on all calls through the Flash bridge after files have been added to the queue.
I've tracked this down to SWFUpload's famous sensitivity about DOM manipulation. It appears that if the Flash browse button is located anywhere near elements in the DOM that are manipulated, or is manipulated itself, the Flash bridge breaks.
The solution to this is to move the Flash browse button outside of the Uploader container into a location where it is isolated.
Environment
None
Attachments
3
100% Done
Activity
Show:
Michelle D'Souza February 28, 2011 at 9:47 PM
Closing issues that were fixed in 1.1.2
d October 9, 2009 at 6:02 PM
I have narrowed the problem down to the following: If the uploader is not visible on the load of the page, then the swf file isn't visible.
d October 9, 2009 at 2:06 PM
We at Sakai are using the fluid uploader inside of a jquery ui accordion. Everything worked fine in the old version (except in firefox 3.5) but since the fix we are not able to see the swf file (which contains the browse button). So we can not launch the browse window to select multiple files.
When we put our html code outside of the jquery ui accordion, everything works fine.
Eli Cochran October 2, 2009 at 5:30 PM
I've reviewed Colin Clark's changes for and and tested the code both locally and off the server using FF3.5. Looks good to me.
Uploader's underlying upload manager, SWFUpload has regressed in Firefox 3.5. As a result, it is throwing exceptions on all calls through the Flash bridge after files have been added to the queue.
I've tracked this down to SWFUpload's famous sensitivity about DOM manipulation. It appears that if the Flash browse button is located anywhere near elements in the DOM that are manipulated, or is manipulated itself, the Flash bridge breaks.
The solution to this is to move the Flash browse button outside of the Uploader container into a location where it is isolated.