Comment 6 for bug 1227777

This appears to have been fixed by switching to oxide, which is built on the chromium content API, which seems to allocate the first few percents of the progress to waiting for a response from the server, as desired.