WebExtensions/FAQ: Difference between revisions
Jump to navigation
Jump to search
| 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. | 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. 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. | ||
Revision as of 19:48, 24 August 2015
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. In other areas it doesn't. 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.