This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#updating-an-application-cache Comment: Maybe progress should be named fetchcachefile or some such instead as that seems much more closely to what is used for. However, I don't quite understand why you would not want more detailed progress events here so you can show a progress bar to the user while updating the application. Posted from: 213.236.208.22
Unless you do one progress bar per file (unlikely, given that each file will typically only take 250ms), you don't know how many bytes the total will be. So the only way to do a progress bar that I can see is to use the number of files as the total. Which is what the spec does. Not sure why we'd use another event name though; can you elaborate?
Updating a progress bar every 250ms will give you bad UI. You might as well not have it then I think. From experience with progress events for XMLHttpRequest you want something about every 50ms to get a smooth download bar. The reason I suggested another name is that progress is very generic and we might want to use it for something else in the future. The function here is also very specific so it seems better to keep the name consistent with that.
Anne, you misread what Ian wrote. Anyway, the progress bar update period should be on behalf of the UA according to the capacity of the computer running it, every 50ms could harm the user experience a little bit more on busy computer.
I don't think I did. UAs are of course always allowed to do things differently in face of limited resources though dispatching an event every 50ms is really not that bad. Consider all the animation effects people implement with time outs that run every 15ms.
We don't have the data, we can't just artificially make up the data. So I don't see how to make it any better. _If_ someone wants to make a progress bar of any kind, they'll need the data. That's the only use case I had in mind when making this event available. So it makes sense to call it 'progress' IMHO.