WebExtensions/FAQ: Difference between revisions
Jump to navigation
Jump to search
Wmccloskey (talk | contribs) (add some questions) |
|||
| 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. 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. | 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. | ||
=== Why WebExtensions and not Jetpack? === | |||
=== How will WebExtensions be cross-browser if you're extending Google's API === | |||
=== Which add-ons will stop working after the deprecation? === | |||
=== I'm writing a new extension today. What API should I use? === | |||
=== Why does Mozilla hate power users? === | |||
Talk about how we're not trying to limit what extensions can do. | |||
=== I already have a XUL extension. How is this not terrible news for me? === | |||
Talk about how we want to break extensions less. | |||
=== Why deprecate XUL now? Firefox is still using it internally. === | |||
Revision as of 20:00, 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.
Why WebExtensions and not Jetpack?
How will WebExtensions be cross-browser if you're extending Google's API
Which add-ons will stop working after the deprecation?
I'm writing a new extension today. What API should I use?
Why does Mozilla hate power users?
Talk about how we're not trying to limit what extensions can do.
I already have a XUL extension. How is this not terrible news for me?
Talk about how we want to break extensions less.