WebExtensions/FAQ: Difference between revisions

→‎Won't this limit experimentation?: reflect the actual commitment to give add-on developers freedom to innovate
(venn diagram link)
(→‎Won't this limit experimentation?: reflect the actual commitment to give add-on developers freedom to innovate)
Line 25: Line 25:


=== Won't this limit experimentation? ===
=== Won't this limit experimentation? ===
As is, it will. We are trying to devise a system that will allow for extension authors to have the flexibility to implement features that the WebExtension API doesn't currently allow. [https://discourse.mozilla-community.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457 Some discussion] has already begun.  The intent is for add-on authors to experiment through this mechanism with the knowledge that there are no guarantees of compatibility between Firefox releases and use that to inform future additions to the WebExtension API
If WebExtensions were ultimately limited to the Chrome model, it would. But we're actually designing a system providing extension authors with the flexibility to implement innovative features that the WebExtension API doesn't currently allow. [https://discourse.mozilla-community.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457 Some discussion] has already begun.  The intent is for add-on authors to experiment through this mechanism, with the knowledge that there are no guarantees of compatibility between Firefox releases, and use that to inform future additions to the stable WebExtension API.


=== I already have a XUL extension. How is this not terrible news for me? ===
=== I already have a XUL extension. How is this not terrible news for me? ===
51

edits