Confirm
1,605
edits
Changes
m
→WebExtensions Decision: vision
Unlike the web platform, we don't expect every browser to implement every aspect of WebExtensions in the same way. But, even without perfect compatibility between browsers, a common API still has many advantages for extension developers. If developers stay within the common API, their extensions should work with minimal (or no!) modifications across browsers. Even if developers choose to use browser-specific APIs, their extensions may be usable on other browsers through feature detection and fallbacks. As an example, an extension using a toolbar API might be able to fall back to a browser action API on other browsers.
=== What do you mean by "Extending the capabilities of Firefox to interact with web content" in your [https://wiki.mozilla.org/WebExtensions/Vision vision statement]? ===
It means helping people use the Web, like making it easier to browse, manage browsing, and use websites/web apps/content. Our focus with the WebExtensions API is about extending these capabilities rather than making Firefox an application platform.
=== Why WebExtensions and not Jetpack? ===
