WebExtensions/NewAPIs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Added link to WebExtensions API policy page)
(Removed a point that became redundant when 57 was released.)
Line 14: Line 14:
* Still want to file a new API? You can do so [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged here].
* Still want to file a new API? You can do so [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged here].


Here are some reference materials you might find helpful:
Goals are set out in the [[WebExtensions/Vision|vision document]].
* The [[WebExtensions/Vision|vision document]] lays out the goals of WebExtensions
* If you are expecting a bug before Firefox 57, please check out the [https://mzl.la/2qKVGuA roadmap document].

Revision as of 19:08, 6 February 2018

You want to request a new API for WebExtensions?

Great. But please read through the following before filing a bug:

  • If you are migrating your add-on to WebExtensions, please check this page to see if all the APIs you need are already available.
  • If you don't find what you need, please check the list of approved APIs and add yourself to the bug that applies to you to track its progress.
  • Join the dev-addons mailing list to find out which APIs are being triaged every week so you can follow along or provide input.

If none of these options address your situation, consider filing an API request. Before you do, please keep in mind:

  • New API must meet the guidelines outlined the WebExtensions API Policy. Please review it.
  • We do try to review all incoming API requests, but it takes time, so please be patient.
  • Do a search to see if the bug exists already.
  • Still want to file a new API? You can do so here.

Goals are set out in the vision document.