Bug 147598 - AppCache can fire both "cached" and "noupdate" event for the same manifest revalidation.
Summary: AppCache can fire both "cached" and "noupdate" event for the same manifest re...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-03 16:13 PDT by Brady Eidson
Modified: 2015-08-03 16:52 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brady Eidson 2015-08-03 16:13:41 PDT 
AppCache can fire both "cached" and "noupdate" event for the same manifest revalidation.

The spec (http://www.w3.org/TR/2011/WD-html5-20110525/offline.html) says that both "cached" and "noupdate" are terminal events - "Last event in sequence" - so it seems this is wrong.

To see this reproduce, run the layout test http/tests/appcache/identifier-test.html and notice that the event handler is called twice, once for each of these events.
Comment 1 Alexey Proskuryakov 2015-08-03 16:52:35 PDT 
Turns out that it's called twice because a handler is installed in two windows, and each gets an event.