Closed
Bug 1248455
Opened 9 years ago
Closed 9 years ago
Google Chrome has better diagnostics when manifest.json is invalid
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1224591
People
(Reporter: wbamberg, Unassigned)
Details
Attachments
(1 file)
159.63 KB,
image/png
|
Details |
I tried an add-on that had an extra trailing comma in the manifest, like this:
"permissions": [
"tabs",
]
Trying to install in Firefox, I get a dialog saying:
"This add-on could not be installed because it appears to be corrupt"
Trying to install in Chrome, I a dialog showing me exactly where the error was, and letting me retry after fixing it. See the attached screenshot.
Comment 1•9 years ago
|
||
I think, if we want people to write WebExtensions, showing errors like this will be _very_ important…
Flags: blocking-webextensions?(amckay)
Comment 2•9 years ago
|
||
We actually do show these kinds of errors in the Browser Console, they're just not very easy to find. I think there are at least a couple of bugs about this already.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Flags: blocking-webextensions?(amckay) → blocking-webextensions+
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•