Closed Bug 477747 Opened 13 years ago Closed 13 years ago
app cache "noupdate" event fired too early for master entries
When a manifest update is triggered by a master entry (an entry that includes the manifest attribute but was not explicitly listed in the manifest itself), we schedule a partial update to add the master entry to the application cache, and then fire a "noupdate" event. The spec says that we should fire noupdate after the master entry has been successfully added to the cache. The attached patch fixes this by having the main update manage/run the partial update, rather than scheduling it with the main service. This patch also correctly associates pending master documents before scheduling the partial update. That bit is really small, and if we end up not wanting the whole thing for 3.1, I'll spin that into a new bug.
Not blocking, jst said he'd review the patch.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
An approval of this patch should also include an approval of the regression fix in bug 482370
Comment on attachment 361460 [details] [diff] [review] v1 a191=beltzner
Attachment #361460 - Flags: approval1.9.1? → approval1.9.1+
You need to log in before you can comment on or make changes to this bug.