Last Comment Bug 757613 - Use manifest.webapp instead of manifest.json
: Use manifest.webapp instead of manifest.json
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: DOM: Apps (show other bugs)
: Other Branch
: All All
: -- normal (vote)
: mozilla15
Assigned To: [:fabrice] Fabrice Desré
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-22 14:19 PDT by [:fabrice] Fabrice Desré
Modified: 2012-12-06 17:35 PST (History)
6 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
patch (1.21 KB, patch)
2012-05-22 14:19 PDT, [:fabrice] Fabrice Desré
anant: review+
Details | Diff | Splinter Review

Description [:fabrice] Fabrice Desré 2012-05-22 14:19:45 PDT
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.
Comment 1 Anant Narayanan [:anant] 2012-05-22 14:33:19 PDT
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.
Comment 2 [:fabrice] Fabrice Desré 2012-05-22 14:39:20 PDT
https://hg.mozilla.org/integration/mozilla-inbound/rev/90f5320604af
Comment 3 Ed Morley [:emorley] 2012-05-23 05:04:57 PDT
https://hg.mozilla.org/mozilla-central/rev/90f5320604af
Comment 4 Jason Smith [:jsmith] 2012-07-17 20:24:01 PDT
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.

Note You need to log in before you can comment on or make changes to this bug.