WebExtensions/FAQ: Difference between revisions

wording
(editing)
(wording)
Line 1: Line 1:
=== It sounds like you're copying Google... ===
=== It sounds like you're copying Google... ===
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. However, there will be differences. We won't implement all of Chrome's APIs, and we will implement our own APIs. Imagine the APIs as a Venn diagram. In the middle are cross-browser APIs for content scripts, tabs, and windows. In the Firefox side are APIs for toolbars and sidebars. On the Chrome side are APIs for Google's cloud services.
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. However, there will be differences. We won't implement all of Chrome's APIs. And Chrome is unlikely to implement some of the APIs we add. Imagine the APIs as a Venn diagram. In the middle are cross-browser APIs for content scripts, tabs, and windows. In the Firefox side are APIs for toolbars and sidebars. On the Chrome side are APIs for Google's cloud services.


=== How will WebExtensions be cross-browser if you're extending Google's API? ===
=== How will WebExtensions be cross-browser if you're extending Google's API? ===
Confirmed users
130

edits