Closed Bug 757613 Opened 12 years ago Closed 12 years ago

Use manifest.webapp instead of manifest.json

Categories

(Core Graveyard :: DOM: Apps, defect)

Other Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla15

People

(Reporter: fabrice, Assigned: fabrice)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
We promote the use of manifest.webapp everywhere (and switched to that in gaia), so let's align the implementation here also.

This uses .webapp when installing new apps, and supports .json and .webapp when reading to not lose previously installed apps.
Attachment #626181 - Flags: review?(anant)
Comment on attachment 626181 [details] [diff] [review]
patch

Looks good to me, though it does feel a bit clunky having that one bit of backwards-compatibility code in there. Hopefully we won't need it anymore once some form of app sync lands.
Attachment #626181 - Flags: review?(anant) → review+
https://hg.mozilla.org/mozilla-central/rev/90f5320604af
Assignee: nobody → fabrice
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla15
Whiteboard: [qa+]
This patch only modifies the DOM Registry, correct? If so, is there any way to verify this from an end-user perspective?

I know installing an app on desktop still produces a "manifest.json" in the APPDATA folder for windows with this patch.
Whiteboard: [qa+] → [qa?]
Component: DOM: Mozilla Extensions → DOM: Apps
Whiteboard: [qa?]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.