Closed
Bug 1323225
Opened 8 years ago
Closed 7 years ago
Document need for WebExtension ID on MDN
Categories
(Developer Documentation Graveyard :: Add-ons, defect)
Developer Documentation Graveyard
Add-ons
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glasserc, Unassigned)
References
Details
Although WebExtensions' IDs are "non-mandatory", under certain circumstances, certain APIs cannot function correctly withuot an ID. However, the documentation on when to use an ID in your WebExtension manifest and how is a little thin. :andym suggests that we should update https://developer.mozilla.org/en-US/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID as well as any API documentation for the APIs listed in https://github.com/mozilla/addons-linter/issues/1064. Ideally, the MDN pages also explain that although https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications says that you cannot use this key in Chrome, what that means is that Chrome will report an error in your manifest, but load the extension anyhow (so, it's safe to use).
Updated•8 years ago
|
Keywords: dev-doc-needed
Updated•7 years ago
|
Component: WebExtensions: Untriaged → Add-ons
Product: Toolkit → Developer Documentation
Comment 1•7 years ago
|
||
I've had a go at this. In particular here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID#When_do_you_need_an_Add-on_ID https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/storage/sync identity.getRedirectURL isn't documented yet. Please let me know if this covers it.
Flags: needinfo?(eglassercamp)
Reporter | ||
Comment 2•7 years ago
|
||
Looks good to me, thanks!
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(eglassercamp)
Resolution: --- → FIXED
Updated•7 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•