Closed
Bug 477692
Opened 15 years ago
Closed 15 years ago
applicationCache sending "obsolete" on new cache groups
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: dcamp, Assigned: dcamp)
Details
(Keywords: fixed1.9.1)
Attachments
(1 file)
3.73 KB,
patch
|
jst
:
review+
jst
:
superreview+
jst
:
approval1.9.1+
|
Details | Diff | Splinter Review |
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)
Comment 1•15 years ago
|
||
Not blocking, but we should take this patch...
Flags: blocking1.9.1? → blocking1.9.1-
Updated•15 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•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/87f99c57b51f http://hg.mozilla.org/releases/mozilla-1.9.1/rev/c61ffd6cd625
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•