147598 2015-08-03 16:13:41 -0700 AppCache can fire both "cached" and "noupdate" event for the same manifest revalidation. 2015-08-03 16:52:35 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 1 beidson webkit-unassigned ap oldest_to_newest 1114426 0 beidson 2015-08-03 16:13:41 -0700 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. 1114441 1 ap 2015-08-03 16:52:35 -0700 Turns out that it's called twice because a handler is installed in two windows, and each gets an event.