-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.6.0-HF15, 5.7.1
-
Component/s: Seam / JSF UI
The problem is random, and actually I was only able to reproduce it after switching to a slower laptop ...
Anyway, the problem description is :
- you upload several files via D&D
- upload is actually done ok
- but the upload dialog remains displayed whereas it should detect that file upload is completed
When adding logs during an upload of 4 files, here is what we get :
starting upload for file 0 readyStateChange event on file upload 0 (state : 1) starting upload for file 1 readyStateChange event on file upload 1 (state : 1) starting upload for file 2 readyStateChange event on file upload 2 (state : 1) delaying upload for next file(s) 3+ since there are already 3 active uploads progress event on upload of file 0 --> 100% readyStateChange event on file upload 2 (state : 1) readyStateChange event on file upload 2 (state : 1) readyStateChange event on file upload 2 (state : 1) progress event on upload of file 1 --> 100% readyStateChange event on file upload 2 (state : 1) readyStateChange event on file upload 2 (state : 1) readyStateChange event on file upload 2 (state : 1) progress event on upload of file 2 --> 100% readyStateChange event on file upload 2 (state : 2) readyStateChange event on file upload 2 (state : 3) readyStateChange event on file upload 2 (state : 4) upload of file 2 completed restart pending uploads starting upload for file 3 readyStateChange event on file upload 3 (state : 1) delaying upload for next file(s) 4+ since there are already 3 active uploads progress event on upload of file 3 --> 100% readyStateChange event on file upload 3 (state : 2) readyStateChange event on file upload 3 (state : 3) readyStateChange event on file upload 3 (state : 4) upload of file 3 completed
This looks like the readyStateChange with state 2 is never fired for files 0 and 1.
This explains why the upload for file 0 and 1 are never considered finished.
The problem is probably tied to a recent fix : NXP-11036
=> load event lay be buggy on some browser, but it looks like
=> onreadystatechange is also buggy
For now the solution seem to be to use the progress event ...
- depends on
-
-
- Resolved
-
