Bug 147598

Summary:	AppCache can fire both "cached" and "noupdate" event for the same manifest revalidation.
Product:	WebKit	Reporter:	Brady Eidson <beidson>
Component:	Page Loading	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED INVALID
Severity:	Normal	CC:	ap
Priority:	P2
Version:	528+ (Nightly build)
Hardware:	Unspecified
OS:	Unspecified

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.