Mozilla Add-ons Community Blog
Categories: developers jetpack releases sdk

Announcing Add-on SDK 1.11!

6 responses

The Jetpack team is terribly pleased to announce the immediate availability of SDK 1.11. You can download the SDK directly in either zip or tarball format.

What’s new?

SDK 1.11 is the most significant release in recent memory, largely due to the enhancements we’ve made to the page-mod module. Page-mod is easily one of the most popular and powerful modules we provide in the SDK, and we think these enhancements bring the module’s capabilities in line with what developers are demanding:

  • When a user installs an add-on that implements a page-mod, any existing pages that would match your include criteria are applied instantly.
  • Conversely, when an add-on is uninstalled any live page-mods are removed dynamically.
  • Page-mod now features fine-grained control over which documents are injected not only based on url, but also whether the document is loaded into an frame/iframe or is the top-level document.

For a full explanation please see these excellent blog posts from Alex and Matteo, and of course the docs. For more new features and a list of the bug fixes that are shipping in this release, please see the Release Notes and the full documentation.

Some interesting stats about this release ( from the github history between the 1.10 & 1.11 tags ):

  • 201 changes in 60 pull requests between tags 1.10 and 1.11
  • Community contributors: Arky & Gregg Lind

As always, we’d love to hear from you about your experiences with this release. You can contact us in a variety of ways:

post to our discussion group
chat with us on irc.mozilla.org #jetpack
report a bug
check out the source and contribute bug fixes, enhancements, or documentation

For more information on the Jetpack Project check out our wiki.

6 comments on “Announcing Add-on SDK 1.11!”

  1. tom jones wrote on

    did cross-domain privileges for content scripts (mentioned in Alex’s post) make it into 1.11 or is it planned for 1.12 or even later?

    1. Jeff Griffiths wrote on

      Excellent question! The platform changes we needed in order to make this work were shipped in Firefox 16, but the additional feature in the SDK itself will not ship until SDK 1.12 in 6 weeks. If you want to test this feature out in the meantime, it is now ( as of today ) available on the stabilization branch in Github.

      1. tom jones wrote on

        unfortunately, i use the amo builder, so i’ll wait the 7-8 weeks..

        btw, why isn’t the builder team more integrated with the sdk team? why don’t you coordinate your releases, and why can’t we use pre-release sdk versions in the builder?

        1. Jeff Griffiths wrote on

          Builder isn’t under active development currently, so when we need changes made to it to keep it up to date these changes are done only as-needed and on borrowed time, as the development resources for Builder have largely been re-assigned to other projects.

          I would like to point out that we had some success today in updating Builder to 1.11 with relatively little drama – this is live now.

  2. John Nagle, Silicon Valley, CA wrote on

    SDK 1.11 is a big step forward. Several major bugs I’ve been complaining about for almost a year are at last fixed. Mutation observers finally work. The “content script being randomly reused” bug is fixed. The timeout bug that crept into a beta SDK was fixed before the final version shipped. I am much relieved.

    1. Jeff Griffiths wrote on

      Thanks for the comment ( and sorry for the lateness of my reply, I just got back from vacation ) – I’m glad you are relieved and that the SDK is working well for you now.