7775 2009-09-30 16:02:38 +0000 are the extra events needed when status is checking or downloading 2010-12-01 15:28:00 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Linux VERIFIED INVALID NE P2 normal --- 1 annevk ian ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 27950 0 annevk 2009-09-30 16:02:38 +0000 Why do the events in substep 4 and 5 need to be dispatched if the algorithm is already in progress elsewhere? Because if the algorithm is in progress the ApplicationCache update will get events on that already. 27972 1 annevk 2009-10-01 13:53:33 +0000 Another thing to consider here is that currently only the "cache host" that started the update process can show progress UI. Is that really desired? If the user switches tabs shouldn't it be able to see some kind of progress there too? Maybe if people want to do that they should use Web Workers? Maybe add a note somewhere if that is the case? Also, might it be good to explicitly tell an application author that an update is already in progress somewhere? E.g. by instead of feeding the author checking and downloading events that the author would get anyway (as far as I can tell) maybe give a specific event such as alreadyupdating. 28475 2 ian 2009-10-18 22:08:59 +0000 All the cache hosts get all the events. I don't understand this bug report.