Delayed retries appear as pending with progress > 0
Delayed retries appear as pending with progress > 0

By @tpodom to resolve #61.

When using the delayed retry interval a chunk will be reset with the
xhr as null.
As a result, the chunk appears as pending and is available to be sent
once another
finishes.  However, if it gets sent and then the timer fires the same
chunk will be
sent a second time (possibly simultaneously).

Since the loaded value isn't cleared on abort the progress for a chunk
pending
retry also reports its progress as how far the chunk got before the
failure.  This
can result in a chunk being 100% sent but failed on the server and the
fileSuccess
firing before the chunk is actually completed.

szelcsanyi/resumable.js,szelcsanyi/resumable.js,Parent5446/resumable.js,atlassian/resumable.js,flowjs/flow.js,codecentric/flow.js,atlassian/resumable.js,jasonmorganson/flow.js,sahat/flow.js,vsivsi/resumable.js,dshefchik/flow.js,manoj-nama/flowplus,SuberFu/flow.js,evilaliv3/flow.js,team-enceladus/resumable,flowjs/flow.js,gdseller/resumable.js,SuberFu/flow.js,wyxacc/resumable.js,danmindru/flow.js,Karankang007/flow.js,jerlinjames/flow.js,23/resumable.js,roccivic/flow.js,fjalex/resumable.js,23/resumable.js,Symplicity/flow.js,cadam-telpay/flow.js,23/resumable.js,Parent5446/resumable.js,gdseller/resumable.js,jimdoescode/resumable.js,Klaudit/resumable.js,manoj-nama/flowplus,team-enceladus/resumable,wyxacc/resumable.js,muhghazaliakbar/flow.js,team-enceladus/resumable,vsivsi/resumable.js,fjalex/resumable.js,Klaudit/resumable.js,eric-seekas/flow.js