Closed Bug 900584 Opened 12 years ago Closed 12 years ago

Marketplace should know about "chrome" property in webapp manifest

Categories

(Marketplace Graveyard :: Validation, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED
2013-08-13

People

(Reporter: Harald, Assigned: basta)

Details

Similar to the new "origin" property, Marketplace should know about "chrome". Bug 895826 adds a "chrome" property to the webapp manifest, currently only allowing {"navigation": true}. This enabled apps to have platform-provided back navigation. Validator should recognize "chrome" as valid property and "navigation" as its only valid Boolean key. App submission should know that "chrome" requires 1.1 (similar to "origin").
"chrome" will make roughly every second Marketplace submission from partners easier. As soon as it lands in v1-train partners will want to use it and submit their app.
Severity: normal → major
OS: Mac OS X → All
Hardware: x86 → All
Please provide URLs to appropriate docs pages that the validator should link to.
Severity: major → normal
Priority: -- → P3
Documentation is tracked in bug 901003, I'd recommend not block on that though.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee: nobody → mattbasta
Target Milestone: --- → 2013-08-13
Please add STR here or mark it with [qa-] if no QA is needed.
Flags: needinfo?
1. Submit an app with the "chrome" field in the manifest 2. Check that you don't get a warning for it.
Flags: needinfo?
Verified as fixed in https://marketplace-dev.allizom.org/developers/submit/ on FF26 (Win 7). Postfix screencast http://screencast.com/t/qx0ypcQt Closing bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.