Closed
Bug 758083
Opened 13 years ago
Closed 13 years ago
Make manifest paths consistent with openwebapps manifest paths
Categories
(Firefox Graveyard :: SocialAPI, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markh, Unassigned)
References
Details
We should make the manifest consistent with OWA - https://developer.mozilla.org/en/Apps/Manifest#path-handling and specifically, "All fields that hold paths in the manifest must be absolute paths (for example, '/images/myicon.png'), and are served from the same origin as the app."
So in practice this means:
* ALL paths in the manifest must be absolute and relative to the origin.
* If we really need URLPrefix, it should follow the same rules. However, ideally this would actually be optional
Comment 1•13 years ago
|
||
cool! pushed to git and hg. URLPrefix is gone, replaced with the ability to define origin in a builtin manifest.
https://github.com/mozilla/socialapi-dev/commit/6a35483cec70a946846125e38f2ec49752dba842
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•