Author: neilk
Description:
If you select more than the configured maxUploads, the UI will add all the files anyway.
There is some asynchrony that was not an issue before.
- an "upload" is not necessarily a filled upload. The file input hovering over the "add a file" button belongs to an unfilled upload. Filled uploads are added to the wizard's list of uploads. Unfilled uploads are just sort of UI elements waiting to turn into the real thing.
- in newUpload(), there is a check of the wizard's count of uploads; it returns false if current length = max
- but, there is a very slight delay between creating a new upload and marking it filled (this is async). And the upload is only added to the wizard at the "filled" trigger event
- there is some attempt to fix this with the change() invocation for synthetically created providedFile -- maybe this should be the filled trigger. Or both?
Version: unspecified
Severity: normal