Add-on Compatibility for Firefox 19

Firefox 19 will be released on February 19th. Here’s the list of changes that went into this version that can affect add-on compatibility. There is more information available in Firefox 19 for Developers, so you should read that too.


Private Browsing

Private Browsing Mode is changing to support private and non-private windows opened at the same time. This means that many XPCOM interfaces and other functions are changing to support it. The changes are mostly new parameters that tell the function which context it is being called from, so that it can work accordingly.

There’s more information about the new private browsing in these docs: Supporting PBM, and Updating add-ons broken by PB changes.



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

The automatic compatibility validation and upgrade for add-ons on AMO will happen very soon, so check your email if you have an add-on on AMO.

7 comments on “Add-on Compatibility for Firefox 19”

  1. Brian LePore wrote on

    I was just emailed that my addon “broke” … sort of. The validation service keeps on hitting the 90 second limit. My extension is purposely packed with a variety of JavaScript frameworks that can be selected by users for various things. I can understand why it hits the limit. I recently had to reduce the number of frameworks supported just so that it could pass the validation service when I uploaded a new version.

    1. Jorge Villalobos wrote on

      Yes, unfortunately this can happen for very complex or large add-ons. The only solution is to make the add-on smaller or simpler. If this is preventing you from uploading a new version, we have ways to override it. If you emailed us, expect a response soon.

  2. Nani Games wrote on

    some addons still not work 🙁
    like download manager .. and java now also .. close
    i sent a report with the bugs

  3. Riclo wrote on

    Download manager doesnt work!!!
    Please make an upgrade to fix it.

  4. Barry wrote on

    Why has PrivacySuite stopped working on every upgrade of firefox?

    1. Jorge Villalobos wrote on

      Privacy Suite needs to be updated on every release because it uses binary components, activating the strict compatibility mode in Firefox. However, it looks like they are doing a good job keeping up to date. It seems like you should only have compatibility problems if you use Aurora or Nightly. Is that your case?

  5. AC wrote on

    Just encountered as issue with nsiIdleService:

    There was a change in v16 in nsiIdleService that can break extensions. This has not been mentioned in the blog or tested the compatibility updates as far as I can see.

    It is (now) documented on the nsiIdleService page:

    The observer will get an ‘idle’ notification when the user is idle for that interval (or longer), and receive a ‘back’ (Gecko 3 to 15) or ‘active’ (Gecko 16+) notification when the user starts using their computer again.

    Existing extensions that monitor idle and expect ‘back’ might be missing the return from idle mode.