The default bug view has changed. See this FAQ.

Handle the MozApplicationManifest event in b2g/

RESOLVED FIXED in mozilla11

Status

()

Core
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: vingtetun, Assigned: vingtetun)

Tracking

(Blocks: 1 bug)

Trunk
mozilla11
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 580365 [details] [diff] [review]
Handle MozApplicationManifest

In order to use appcache we need to support the MozApplicationManifest event.
Attachment #580365 - Flags: review?(jones.chris.g)
Comment on attachment 580365 [details] [diff] [review]
Handle MozApplicationManifest

The cache for packaged apps will work slightly differently than this, but we need this support regardless.
Attachment #580365 - Flags: review?(jones.chris.g) → review+
(In reply to Chris Jones [:cjones] [:warhammer] from comment #1)
> Comment on attachment 580365 [details] [diff] [review]
> Handle MozApplicationManifest
> 
> The cache for packaged apps will work slightly differently than this, but we
> need this support regardless.

Uh? Can you explain more. With Fabrice we have elaborate a plan of using the pre-built OfflineCache/ directory inserted into the default profile - and for info I'm very close to have it working.
The app manifest/package should specify cached resources, not the document element of the app itself.  We'll need to add code to support that.
Blocks: 709468
Flags: in-testsuite?
OS: Linux → All
Hardware: x86_64 → All
Target Milestone: --- → mozilla11
Version: unspecified → Trunk
Attachment #580365 - Flags: checkin+
https://hg.mozilla.org/mozilla-central/rev/c7ffe3549389
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Updated

5 years ago
Assignee: nobody → 21
You need to log in before you can comment on or make changes to this bug.