Add-ons Blog

SDK 1.3 performance impact

Recently Jorge Villalobos ran some tests to measure the impact of using the SDK on Firefox start-up time. Jorge published his finding to the Jetpack google news group. His results were encouraging:

The results were very favorable this time, with the
empty add-on adding only 1.8% (11ms) to startup, and Infocon adding only
3.6% (22ms), on average. As a reference point, after our initial tests
we decided that 7% was roughly the line where add-on startup overhead
stopped being “Excellent” and began being just “Good”.

The methodology of these tests was to measure Firefox start-up time under three different scenarios:

  1. using a clean profile with no addons enabled.
  2. with a single ‘empty’ SDK-based add-on enabled.
  3. with a non-trivial add-on enabled.

The great thing about this is that we now have solid data that indicates SDK version 1.3 itself has little effect on Firefox start-up time however, as Jorge suggests, there is much more testing that could be done. In particular, we should continue to run these tests to ensure that future versions of the SDK do not degrade start-up performance as we add new modules or make infrastructure changes to the SDK.

If you’re curious, we test start-up impact using Talos according to this methodology:

https://developer.mozilla.org/en/Measuring_Add-on_Startup_Performance

If you want to run the tests yourself, Talos is relatively straightforward to set up:

https://wiki.mozilla.org/StandaloneTalos#How_to_set_up_Talos_for_testing_at_home

I should warn you that the tests themselves can take quite some time to complete!

Just Landed: Simple Prefs API

On November 28, Myk Melez closed pull request 270, which added the new ‘simple-prefs’ module to the Addon SDK. This addition to the SDK’s addon-kit apis is special for a couple of reasons:

  • The ability to add a simple preferences panel to an SDK-based add-on has been a major gap in functionality in the SDK. We’re very happy to be moving forward adding features like this.
  • This code was contributed entirely from the community, in particular community contributors Hernán Colmeiro and Erik Vold.

Read the rest of this entry »

Add-ons Update – Week of 2011/12/07

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

AMO Outage

We had a significant outage on our site (and others) earlier this week, which affected some add-on operations such as compatibility checks. AMO is back to normal now and we’re looking into ways of avoiding this from happening again.

The Review Queues

  • Nominations for full review at the moment are being processed slower than usual. Most nominations are taking less than 5 weeks to review.
  • Most updates are being reviewed within 10 days.
  • Most preliminary reviews are being reviewed within 3 weeks.

These stats are taken from the last queue report:

  • 67 new nominations that week. 224 nominations in the queue awaiting review.
  • 101 new updates that week. 135 updates in the queue awaiting review.
  • 78 new preliminary review submissions that week. 115 preliminary submissions in the queue awaiting review.

If you’re interested in joining the AMO Editors team and help us review add-ons, please visit our wiki page.

Firefox 10

The Firefox 10 compatibility post is here. The compatibility bump to Firefox 10 was run last week, so any add-ons with compatibility under 10.* should be tested and manually upgraded in the Developer Hub, if possible.

You can run the standalone compatibility tool if you want to test your add-on yourself or if it isn’t hosted on AMO.

The Add-ons Default to Compatible feature is progressing, and we expect to land for Firefox 10 or 11. Once this is in place, your compatibility worries will be minimized, and we’ll be taking a more active role in letting developers know if their add-ons are incompatible with a new version of Firefox. This feature will be a big win for both developers and Firefox users, so we’re very excited about it.

Jetpack Project: weekly update for Dec. 6th, 2011

Project News

  • As Justin Scott noted here, addons.mozilla.org was down yesterday for some time or was responding very slowly. This seems to have been resolved but Mozilla IT is continuing to monitor the situation.
  • We will be releasing the first beta build of Addon SDK 1.4 some time today. Watch for announcements on the google group.

Quick Stats

Note: the stats above are based on the queries I linked to for each item. If you have suggestions on how these queries might be made more accurate,please comment below. Stats generated at 2011-12-06 14:00:27 PST

Meeting Brief

  • Flightdeck: new release this week including many search enhancements. Will be publishing draft roadmap later today.
  • SDK: Q4 goals review, 1.4b1 will be spun today.
  • UX team dropped by to talk about upcoming UX changes that affect how addons appear in Firefox.
  • discussions next week in SF to talk about the SDK Roadmap for 2012.

Full minutes are available here:
https://wiki.mozilla.org/Labs/Jetpack/Weekly_Meeting/2011-12-6#Minutes

Add-on Compatibility for Firefox 10

Firefox 10 was pushed to the Aurora channel a few weeks ago, so it’s time again to round up all bugs that could be breaking add-on compatibility. It’s a pretty long list this time, but most are removals of obscure and rarely-used XPCOM and DOM interfaces.

As usual, you should check Firefox 10 for Developers for additional information.

DOM Changes

XPCOM Changes

Other Changes

New stuff!

Please let me know in the comments if there’s anything missing or incorrect on these lists. If your add-on breaks on Firefox 10, I’d like to know.

The compatibility bump to Firefox 10 will happen very soon. If you want your add-on to qualify for this, it should be compatible with 9.*. Versions awaiting review also qualify.

Jetpack Project: weekly update for Nov. 29, 2011

Project News

  • Shipped SDK 1.3
  • Landed initial implementation of the Preferences API (although this won’t make it into 1.3).
  • Encouraging results from the latest round of performance testing for SDK-based add-ons.
  • Started planning a new API enabling developers to create pages like the about:addons page: that is, they’re not intended to host normal web pages, so don’t contain all the chrome relevant to normal web pages, such as the awesomebar or bookmarks toolbar.

Quick Stats

Note: the stats above are based on the queries I linked to for each item. If you have suggestions on how these queries might be made more accurate,please comment below. Stats generated at 2011-11-29 14:17:37 PST

Meeting Brief

  • Flightdeck: release this Wednesday, some risky changes
  • SDK: releasing 1.3 this afternoon, merge today from development to stabilization for 1.4
  • Discussed some new features coming up in 1.4/1.5: localization, bypassing content scripts for local content, new XPI file layout.
  • Q4 goal status: mostly on track. Mobile support is at risk: major issue is that new native fennec implementation is changing daily.

Full minutes are available here:
https://wiki.mozilla.org/Labs/Jetpack/Weekly_Meeting/2011-11-29#Minutes

Announcing Add-on SDK 1.3!

The Jetpack team is proud to announce the release of Add-on SDK 1.3! This version of the SDK has some bugfixes, and some new features. Highlights of this release are:

- Fixed a bug where panel-based content scripts don’t work after reloading or changing location
- We now officially support Python 2.7
- Loads of changes and additions to the Add-on SDK documentation

For more details about these and other new features and fixes, please see the Release Notes.

To get started building add-ons with the Add-on SDK, download it, then check out the documentation!

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.

Jetpack Project: weekly update for Nov. 22, 2011

Project News

Quick Stats

Note: the stats above are based on the queries I linked to for each item. If you have suggestions on how these queries might be made more accurate, please comment below.

Meeting Brief

  • Flightdeck: no release this week due to the holiday, working on save bugs.
  • SDK: re-prioritized quarterly goals focusing on L10N and new APIs
  • Wes pointed out Mark Finkle’s Native Add-ons for Mobile post.
  • Report on this weekend’s SDK Hack day.
  • Irakli intends to re-factor codebase using his namespace approach.
  • Alexandre planning to land changes to remove content script requirement for content from the data folder in 1.4

Full minutes are available here:
https://wiki.mozilla.org/Labs/Jetpack/Weekly_Meeting/2011-11-22#Minutes

Add-ons Update – Week of 2011/11/17

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

The Review Queues

  • Nominations for full review at the moment are being processed slower than usual. Most nominations are taking about 6 weeks to review.
  • Most updates are being reviewed within 2 weeks.
  • Most preliminary reviews are being reviewed within 3 weeks.

These stats are taken from the last queue report:

  • 82 new nominations that week. 247 nominations in the queue awaiting review.
  • 116 new updates that week. 149 updates in the queue awaiting review.
  • 66 new preliminary review submissions that week. 104 preliminary submissions in the queue awaiting review.

If you’re interested in joining the AMO Editors team and help us review add-ons, please read the page on How to Apply.

Firefox 8

There’s a bug that affects themes in Firefox 8, in Mac OS X Lion. Please read this blog post if you’re a theme developer.

Firefox 9

The Firefox 9 compatibility post is here. The compatibility bump to Firefox 9 was run weeks ago, so any add-ons with compatibility under 9.* should be tested and manually upgraded in the Developer Hub, if possible.

You can run the standalone compatibility tool if you want to test your add-on yourself or if it isn’t hosted on AMO.

We strongly recommend that you aim to make your add-on compatible with the Firefox version in the Aurora channel. Making your add-on compatible with Aurora qualifies it for our automatic compatibility upgrades, saving you lots of time. If you need more information about this, don’t hesitate to ask.

Firefox 10

Compatibility update coming soon!