]
Ilya Shaikovsky commented on RF-6495:
-------------------------------------
Agree with main issue about automatic upload. if autoclear is false - the upload should
not be started automatically after stopped manually because we do not know which files
actualy to upload all in list or from the last added. fi autoclear is true list empty
after stopped. So if list empty and item added we should start our immediate upload.
fileUpload behaves strange after stopping an upload with flash turned
off
-------------------------------------------------------------------------
Key: RF-6495
URL:
https://jira.jboss.org/jira/browse/RF-6495
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: RichFaces 3.3.0.GA JSF 1.2_12, Seam 2.1.1.GA on Tomcat 5.5.26
Reporter: Daniel Wiell
Assignee: Nick Belaevski
Fix For: 3.3.1
Using this:
<rich:fileUpload allowFlash="false"
immediateUpload="true" autoclear="true"
onuploadcanceled="alert('canceled');"
onuploadcomplete="alert('complete');"
onerror="alert('error');"/>
- Add a large file. Upload will automatically start.
- Stop the upload. IE6 gives an error alert directly. In Chrome, the progress bar locks
up, and after a while, it gives an error alert. In Safari 4, the progress bar empties, no
alerts and the Stop button/link is still active.
- Add a large file again. The upload will not start automatically.
- When manually initiating upload, IE6 gives an error alert.
Enabling flash solves all issues, except that the upload will still not start
automatically the second time around.
I understand that it makes sense to not start the download immediately when autoclear is
false, however with autoclear true it is feels inconsistent not to do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: