cornerli / gwtupload

Automatically exported from code.google.com/p/gwtupload
Other
0 stars 0 forks source link

File content not included in the POST request if SingleUploader.setEnabled(false) is called before or after submit #125

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Use a SingleUploader with auto-commit set to false.
2. Call SingleUploader.setEnabled(false) before or after calling submit()

What is the expected output? What do you see instead?
Looking at the http traffic, the file is not included in the POST request sent 
to the servlet. Everything works fine without the call to setEnabled(false).
I'd like to disable the SingleUploader as I don't want users to be able to 
click on the file input again after submit and until upload is finished. That 
may be a bug, or it may be intended (is there a workaround in that case?).

What version of the product are you using? On what operating system?
GWT 20.4 / gwtupload 0.6.3-compat

Please provide any additional information below.

Original issue reported on code.google.com by p...@linxo.com on 6 Oct 2011 at 10:15

GoogleCodeExporter commented 8 years ago
It is intended.

What you can do is to put a modal upload progress so as the user can not use 
the interface until the file upload was complete.

Another workaround could be to use a Multiuploader with a limit of max file set 
to one (not checked though)

I think we would not change this behavior unless we had more reasons. WDYT?

Original comment by manuel.carrasco.m on 9 Nov 2011 at 11:16

GoogleCodeExporter commented 8 years ago

Original comment by manuel.carrasco.m on 22 Nov 2011 at 3:24

GoogleCodeExporter commented 8 years ago
Sorry for late answer, I went with the modal upload progress. Didn't look at 
the Multiuploader though, does it behave differently ? Would the file be 
included after or before a call to setEnabled() with a MultipleUploader ?
I think it would be good to have a way to disable a SingleUploader regarding 
user interaction only...

Original comment by p...@linxo.com on 22 Nov 2011 at 5:03