-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Collection Upload] Progress bar not updated while async uploading a file #5
Comments
@sescandell I studied the code and it seems it's not a bug.. it just wasn't implemented. |
@sescandell I have an idea how we could implement this: Right now the workflow is:
So we actually have two states:
In order to display a progress bar we need to change the workflow to:
So the possible states are:
|
@sescandell I wonder if this is worth the hassle :) Maybe we just remove the progress bar (since it's useless right now) and "don't fix it if it ain't broken"? Except the progress bar everything seems to work fine. |
Hi @loostro To be honest, I don't remember how this have been implemented... |
@sescandell OK, I'll create a PR replaceing the "progress bar" with a spinning cog icon from FontAwesome icon set. This way User will have some indicator informing that "something is being loaded". |
👍 |
Hi @loostro I just run the code from https://github.com/sescandell/CollectionUploadSample and the progress bar is working well. I think things have been broken since we moved to Bootstrap3. |
I reopened the issue because this is something that was working well before... before I don't know what. I think it was before moving to TB3. JS have not been updated since |
@sescandell OK, I commented out part of JS code in my last PR. So, if you find what was wrong, we have to remove the comments here |
The progress bar is shown initially at
0%
. Then for a few seconds nothing happens. And then the widget is updated with another file.During the upload, progress information should be sent back to the browser and update the progress bar accordingly.
@sescandell Is this a bug in your code, or you didn't implement it? Any tips how this could be fixed?
The text was updated successfully, but these errors were encountered: