Use manifest.webapp instead of manifest.json

RESOLVED FIXED in mozilla15

Status

()

Core
DOM: Apps
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: fabrice, Assigned: fabrice)

Tracking

Other Branch
mozilla15
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 626181 [details] [diff] [review]
patch

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+
(Assignee)

Comment 2

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/90f5320604af

Comment 3

5 years ago
https://hg.mozilla.org/mozilla-central/rev/90f5320604af
Assignee: nobody → fabrice
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla15

Updated

5 years ago
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?]

Updated

5 years ago
Component: DOM: Mozilla Extensions → DOM: Apps

Updated

5 years ago
Whiteboard: [qa?]
You need to log in before you can comment on or make changes to this bug.