Closed
Bug 711538
Opened 13 years ago
Closed 13 years ago
appstore bug with manifests with a BOM
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
FIXED
6.3.6
People
(Reporter: ianbicking, Assigned: kumar)
Details
Reported on the mailing list: This had me stumped for a while. When submitting an app, if you provide a URL to a manifest encoded in UTF-8 with a BOM, it always returns "JSON parse error". If you remove the BOM, it accepts it. Think you might want to fix that - on Windows the BOM is pretty much a standard way of encoding UTF-8 text files. [The store should strip \ufeff from the start of the string if it is present after decoding]
Assignee | ||
Comment 1•13 years ago
|
||
the BOM! nice one.
Component: Public Pages → Developer Pages
QA Contact: web-ui → developers
Target Milestone: --- → 6.3.6
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → kumar.mcmillan
Assignee | ||
Comment 2•13 years ago
|
||
BOMs are all stripped from manifest files now. Also, I added better support for non-ascii manifest encodings. Fixed in https://github.com/mozilla/zamboni/commit/d476408b6eb11a1888952a5a4c75822eb8ef0fba
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•12 years ago
|
||
whoops, we missed the validator: bug 721103
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•