Skip to content
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

Final onProgress value is not always 1 #9

Open
wongbsn opened this issue Jan 29, 2017 · 2 comments
Open

Final onProgress value is not always 1 #9

wongbsn opened this issue Jan 29, 2017 · 2 comments

Comments

@wongbsn
Copy link

wongbsn commented Jan 29, 2017

When listening to on progress, the final value returned is not always 1 when complete. Sometimes, it will return total files minus 1 (ie. for 6 files, the final value returned is sometimes 0.833...).This can also be observed in preloader.percTotal (which is never 1 and always totalFiles - 1 but I don't know if that is an issue).

@ca-miked
Copy link

I'm having the same issue. Seeing erratic progress events that don't seem to correlate mathematically with the total count of urls/files being loaded. @wongbsn Did you find a fix/workaround for this?

@ca-miked
Copy link

This is a sensible solve. You can basically set progress to 1 in the complete handler. Maybe this was by design.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants