Confirmed users
130
edits
Wmccloskey (talk | contribs) (wording) |
Wmccloskey (talk | contribs) (remove redundant stuff) |
||
Line 4: | Line 4: | ||
=== 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? === | ||
Unlike the web platform, we don't expect every browser to implement every aspect of WebExtensions in the same way | 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 will automatically work across browsers. Even if developers choose to use browser-specific APIs, their extensions may be usable on other browsers through feature detection and fallbacks. For example, an extension using a toolbar API might be able to fall back to the browser action API on other browsers. | ||
=== Why WebExtensions and not Jetpack? === | === Why WebExtensions and not Jetpack? === |