![]() Now, here I am working to move as much functionality and data as possible outside of the browser so that, when Classic Theme Restorer dies, I can move to chrome to retain access to a real menu button (rather than a toolbar in a panel) and tabs that collapse down to icons rather than scrolling. Y’know, there was a time when Firefox’s extension API gave birth to innovations like Firebug, which browsers like Chrome and IE rushed to copy. ![]() I mean, there will be such versions, won’t there? If add-ons have to drop xul code, Firefox will do too, right? ByeĪny idea when first developer builds of a xul free Firefox will arrive, so developers can look at is code? Yet again developers are left out in the cold. Note: Edited to better identify specifics around Firefox 53Ĭategories: developers, webextensions 85 responses We’re looking forward to the next year, and will continue to post updates and additional information here on the Add-ons blog.įor more information on Add-ons and WebExtensions, see: If you’re interested in getting involved with the add-on community and WebExtensions, we have a few ways you can do that. There’s a lot of moving parts, and we’ll be tracking more detailed information – including a timeline and roadmap – on the WebExtensions section of the Mozilla Wiki. Throughout the year we’ll expand the set of APIs available, add capabilities to Firefox that don’t yet exist in other browsers, and put more WebExtensions in front of users. ![]() To help ensure any new extensions work beyond the end of 2017, AMO will stop accepting any new extensions for signing that are not WebExtensions in Firefox 53. It’ll be easier to move your add-ons over to and from other browsers with minimal changes, as we’re making the APIs compatible – where it makes sense – with products like Opera, Chrome, and Edge.īy the end of 2017, and with the release of Firefox 57, we’ll move to WebExtensions exclusively, and will stop loading any other extension types on desktop. They’re easier to develop, and you won’t have to learn about Firefox internals to get up and running. WebExtensions are decoupled from the platform, so the changes we’ll make to Firefox in the coming year and beyond won’t affect them. Īs we’ve mentioned, WebExtensions are the future of add-ons for Firefox, and will continue to be where we concentrate efforts in 2017. Finally, we’ve continued to focus on communicating changes to the developer community via direct outreach, mailing lists, email campaigns, wikis, and the add-ons blog. We’ve made a number of changes to our process and products to make it easier to submit, distribute, and discover add-ons through initiatives like the signing API and a revamped Discovery Pane in the add-ons manager. Over the last year, we’ve focused as a community on foundational work building out WebExtensions support in Firefox and (AMO), reducing the time it takes for listed add-ons to be reviewed while maintaining the standards we apply to them, and getting Add-ons ready for e10s. It’s been busy, and we wanted to give everyone an update as well as provide guidance on what to expect in 2017. A little more than a year ago we started talking about where add-ons were headed, and what the future would look like.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |