Changes

Jump to: navigation, search

WebExtensions/NewAPIs

371 bytes removed, 20:49, 2 June 2017
updated information
Great. But please read through the following before filing a bug:
* We've got quite a lot of support alreadyIf you are migrating your add-on to WebExtensions, please checkout check [https://developer.mozilla.org/en-US/Add-ons/WebExtensions /API this page] to see if all the existing APIs]you need are already available.* The goal of WebExtensions is not to support every API and use case from legacy extensions.* For a list of If you don't find what we are aiming for, please check out [[WebExtensions/Vision|the vision document]]* If you are expecting a bug before Firefox 57need, please check out the [[WebExtensions/RoadMapFirefox57|roadmap document]].* Generic or very broad bugs are hard to turn into actionable issues, please try to limit the focus if possible.* Try and do [https://bugzilla.mozillamzl.orgla/query.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Toolkit&component=WebExtensions:%20Android&component=WebExtensions:%20Compatibility&component=WebExtensions:%20Developer%20Tools&component=WebExtensions:%20Experiments&component=WebExtensions:%20Frontend&component=WebExtensions:%20General&component=WebExtensions:%20Request%20Handling&component=WebExtensions:%20Untriaged&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1= a search2qKW0K1 the list of approved APIs] and add yourself to see if the bug exists already before filing if possiblethat 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.
We If none of these options address your situation, you can consider filing an API request. Before you do try to review all incoming API requests, but it takes time, please be patient.keep in mind:
If * The goal of WebExtensions is not to support every use case from legacy extensions. In most cases, the API is controversialfunctionality you need can be built with WebExtensions APIs, but it requires some re-thinking and modification.* Generic or falls outside of very broad bugs are hard to turn into actionable issues. Try to limit the project goals then focus if possible.* We do try to review all incoming API requests, but it will probably takes time, so please be triaged in patient. * Do a [https://mzl.la/2snQxWS search] to see if the bug exists already. Here are some reference materials you might find helpful: * The [[Add-onsWebExtensions/Contribute/TriageVision|design decision needed meetingvision 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].
1,698
edits

Navigation menu