Uploading Media does not show an error when connection is interrupted

[pento]

When using the multi-file uploader, it doesn't show an appropriate error message when the connection is interrupted briefly. Instead, it jumps to "Crunching..." and gets stuck there, giving the impression that the upload was successful.

To reproduce:

• Begin an upload - I suggest a file at least a few MB, so you can see the effect more easily. Also, upload to a remote server, so the connection can be easily killed.
• Upload a few %, then disconnect your computer from the network. I found a 15-20 second disconnect worked most consistently. I was testing with an ethernet connection, I assume WiFi will be the same.
• Reconnect, and observe the upload bar. If it continues counting up, try disconnecting again, for a little longer.

If you successfully reproduced the bug, it jumps to "Crunching...", without showing an error message.

I've reproduced this behaviour in 3.4.2 as well as trunk.

[pento]

I haven't been able to reproduce the same behaviour using the Customizer uploader - I'm not sure if that's due to differences in the JS, or my own timing problems due to the lack of upload progress feedback.

[nacin]

You said this is reproducible in trunk. Was that on media-new.php, or in the Add Media dialog? The latter uses the same (newer) APIs that the customizer uses.

[pento]

Successfully reproduced in trunk with the Add Media dialogue.

[ericlewis]

This would be fitting with the autosave feedback a la 3.6.

[chriscct7]

Good first bug: Is this still reproducible?

[octalmage]

I wasn't able to reproduce this in media-new.php or the Add Media dialog. I tried many combinations, and all of them resulted in an HTTP error. See below:

When I disconnected (using Chrome's dev tools), it jumped to 100% and gave an HTTP error.

[adamsilverstein]

I tried to test this and was unable to reproduce. Here is a screencast where I switch from 2g to no connection in chrome debugger throttling; not the HTTP error message at the top of the screen when the connection fails.

This should probably be closed as invalid.

[desrosj]

I'm also unable to reproduce this. There have been a lot of improvements to how upload failures are handled in recent versions, so this likely is no longer a problem.

If anyone can manage to reproduce this, feel free to reopen with more details to help reproduce.