Closed Bug 452461 Opened 16 years ago Closed 16 years ago

Deleting .part files from beneath a paused download will throw up the "source file could not be read" error

Categories

(Toolkit :: Downloads API, defect)

Product:
Toolkit
Component:
Downloads API
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: stephend, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: polish) 

Spun this off from bug 401846.

If you pause a download and delete its .part, then resume, you'll get the infamous "Download could not be saved, because the source file could not be read" error message.
Flags: blocking1.9.1?
Flags: blocking1.9.0.3?
Version: unspecified → Trunk
Sounds like we could handle this better, but not "blocking" the branch. Normal users aren't going to delete .part files, and if they do an error of some kind is not unreasonable.
Flags: blocking1.9.0.4? → blocking1.9.0.4-
Blocks: 129923
Expected behaviour is to just restart the download from byte 0. Not blocking, but a nice piece of polish.
Flags: blocking1.9.1? → blocking1.9.1-
Keywords: polish
I verified this on Linux and Whimboo (Henrik) verified this on Vista and OSx.

So closing this as WFM.

Regards,
Brahmana.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
As already said, verified with the url given in bug 401846.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.