applicationCache sending "obsolete" on new cache groups

RESOLVED FIXED

Status

()

Core
DOM
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: dcamp, Assigned: dcamp)

Tracking

({fixed1.9.1})

unspecified
fixed1.9.1
Points:
---
Bug Flags:
blocking1.9.1 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

9 years ago
Created attachment 361359 [details] [diff] [review]
fix

When the server sends a 404, we are sending an "obsolete" event.  This is correct if the cache group already exists, but if this is a first-time cache attempt, it should send "error".
Flags: blocking1.9.1?
Attachment #361359 - Flags: superreview?(jst)
Attachment #361359 - Flags: review?(jst)
Not blocking, but we should take this patch...
Flags: blocking1.9.1? → blocking1.9.1-

Updated

9 years ago
Attachment #361359 - Flags: superreview?(jst)
Attachment #361359 - Flags: superreview+
Attachment #361359 - Flags: review?(jst)
Attachment #361359 - Flags: review+
Attachment #361359 - Flags: approval1.9.1+
(Assignee)

Comment 2

9 years ago
http://hg.mozilla.org/mozilla-central/rev/87f99c57b51f
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/c61ffd6cd625
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Keywords: fixed1.9.1
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.