Confirm
1,605
edits
Changes
m
community question
These FAQs are in '''draft''' status.
=== Is it multi-process multiprocess Firefox compatible? ===
Yes, all APIs work with multi process Firefox and are marked as compatible by default.
Some of these are relevant, but come from an FAQ around the decision to implement WebExtensions in August of 2015. They may not still be relevant.
=== It sounds like How are you've made decisions without involving the community input, whyin the development of WebExtensions? ===
We're just getting started with are actively reaching out to developers to find out what APIs they need to migrate to WebExtensions. This helps us figure out which ones will help the greatest number of developers, and have begun with a set of APIs that are commonly used with prioritize them accordingly. The goal is to first reach Chrome so people parity, then go beyond. Anyone can kick the tiresrequest a new API by [https://wiki.mozilla. We don't want to be org/WebExtensions/NewAPIs filing a Chrome copy, and we want to ensure we differentiate while integrating Electrolysis and other initatives into Firefoxbug]. To innovate will require input and assistance from make the communitydecision process as transparent as possible, which we are actively seekinghold a [https://wiki.mozilla.org/Add-ons/Contribute/Triage public triage] of these bugs every other week. The path for WebExtensions will evolve in the coming weeksEach one is labeled "design needed", "approved", monthsor "rejected". If approved, and yearsadditional information on how to write the API is included, and we want the developer community to be a big part of that evolutionan advisor is assigned. Anyone who is interested in working on it can take it.
=== Why are these big changes needed? ===
