FIREFOX DEVELOPER EDITION CHROME EXTENSIONS FULL
“Reviewing is a mostly manual, human process today, and moving an extension from the initial submission to passing a full review that meets our guidelines can be a time-consuming process that can take weeks or months,” Needham writes. Starting with Firefox 42, developers will also have to get their extensions reviewed and signed by Mozilla before they can be deployed. It’s worth noting that these changes won’t apply to developers who use the newer Jetpack SDK to write their extensions (as long as they stay within the confines of Jetpack and don’t try to touch any low-level APIs). This “permissive model,” however, is now going away and add-ons that rely on XUL, XPCOM and the permissive add-on model these technologies enabled will be deprecated within 12 to 18 months. These allowed the browser to be mostly written in JavaScript and ensured that extensions developers got access to a lot of Firefox’s underlying features, but also added complexity. That’s partly due to Firefox’s use of technologies like XPCOM and XUL (for building user interfaces). Writing extensions for Firefox was always a bit more complex than writing something with the same functionality for Chrome. “We would like add-on development to be more like Web development: the same code should run in multiple browsers according to behavior set by standards, with comprehensive documentation available from multiple vendors,” Mozilla’s Kev Needham writes in today’s announcement. The most important of these is the adoption of a new extension API that will be largely compatible with the one currently in use by Blink-based browsers like Chrome and Opera. This so-called WebExtensions API will ensure that developers will only have to make a few small changes to their code for their add-on to run on Firefox.
Mozilla today announced major changes to how Firefox will implement add-ons going forward.
0 kommentar(er)
