Confirm
2,023
edits
Changes
m
You could imagine a Venn Diagram of the two extension APIs. One circle is Chrome's, the other WebExtensions. The overlapping are are basic extension functionality (''give some examples''). Out side of that overlap area would be the areas of differentiation. For example, we don't have much interest in providing easy access to Google's services though WebExtensions. We do however want to support certain use cases that don't seem to be a priority for Google, such as ad-blocking, tab management and time/location shifting content.
→How will the WebExtensions API be different from the Chrome Extension API
The Chrome extension API was designed to work well with process separation and we are certainly taking inspiration from it and copying functionality where it makes sense. In other areas it doesn't.
=== How will the WebExtensions API be different from the Chrome Extension API===
=== Why WebExtensions and not Jetpack? ===
