Add-on Compatibility for Firefox 22

41

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

Update: please read this update for one more compatibility issue that was just discovered.

General

Places

There is much more Places code cleanup happening in 22, so that file system access happens asynchronously. Read the documentation of Places utilities for alternatives of these functions and objects.

XPCOM

New!

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

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

Tags: , , ,

Categories: compatibility, developers, documentation

41 responses {+}

  1. Kohei Yoshino

    > attributes and hasAttributes are now members of Element, instead of Node.

    Node.hasAttributes is still available. (Bug 849661)

      ·   Reply

    1. Jorge Villalobos Author

      Thanks!

        ·   Reply

  2. Kohei Yoshino

    And this article has been published on June 3rd, not May 3rd.

      ·   Reply

    1. Jorge Villalobos Author

      Hmm, must be a WP bug, since I started editing the document last week. Thank you for pointing it out.

        ·   Reply

  3. Paulo Valentim

    I’m not much of a programmer.. Just sad that firefox 22 will break most good features I liked in my favorite add on: http://www.chrisfinke.com/2013/05/06/rss-ticker-13-update/
    I guess I will not be updating when it comes.

    Just my 2 cents
    - Paulo

      ·   Reply

  4. Neal

    Firefox 22 is breaking a lot of functionality especially favicons sync with xmarks.

      ·   Reply

  5. Luke

    What about the major changes in Firefox Developer Tools? No more right click menu on the inspector’s css rules, stack trace has been moved to the top, probably other under-the-hood changes that could break addons that hook into it.

      ·   Reply

    1. Jorge Villalobos Author

      Those changes are unlikely to break add-ons. If you know of any affected cases, please let us know.

        ·   Reply

      1. madrum

        Since V.22 update – Problem of ‘Object moved here’ when navigating on various sites that I used.

        Resolved by disabling ‘Safelinking add-on’

        Will go back to version 21 when I have the time.

          ·   Reply

        1. Jorge Villalobos Author

          What do you mean by “Object moved here”? Can you describe the problem?

            ·   Reply

          1. Xiong

            Hello,

            I have been experiencing the same issue. I will be on one webpage, and then I click a button or link, and when the page loads, the only text I see is “Object Moved This document may be found here.” The word, “here” is a hyperlink. When I click on it, I then get redirected to the page I think I was intended to go.

  6. hanyu

    How about the NPAPI plugin?

    html:

    Version is a property of NPAPI plugin. But in Firefox 22, it errors to get ‘Version’ from:

    document.getElementById(‘testplugin’).Version.

    Is there some changes about it?

      ·   Reply

    1. Jorge Villalobos Author

      I haven’t heard about any changes in this. However, it sounds more like a web compatibility issue than an add-on compatibility issue. Try asking here.

        ·   Reply

      1. hanyu

        ok.Thanks~

          ·   Reply

  7. Evan Edwards

    Firefox 22 definitely broke the add-on “Tab Utilities”.

    Each new whole-number version seems to break that one.
    Unfortunately, it’s one I can’t live without. I’ve directly downgraded to 21.0 without un-installing anything, and that did seem to do the trick.

    Unfortunately, every time a major version comes out, I experience a few broken add-ons, and with the rapid-release program it has become such a pain that I’m officially finished with upgrading Firefox; I intend to stay with 21.0 while I look for a browser that can offer reliable, working add-ons. It’s just out of hand in Mozillaland.

      ·   Reply

    1. tab_util_user

      I totally agree. It’s really disappointing!

        ·   Reply

    2. Robert

      Looks like it’s time to move to Chrome.

        ·   Reply

    3. Patrick

      Agree. Rapid releases breaking essential addons, like tab utilities. Sad.
      I wish there was a “revert” button on the Check for Update screen that would take you back to the previous version of FFox.

        ·   Reply

  8. Alex

    Hello Jorge,

    Our company develops a remote desktop service. Everything was ok until Firefox 22 – it is hanging when trying to run our NPAPI plugin. You can try the plugin at https://techinline.net
    Can you help with this? Where should we see? Thanks!

      ·   Reply

    1. Jorge Villalobos Author

      I’m not aware of any major changes in the plugins platform in Firefox 22. You can try asking in the tech.plugins newsgroup. That’s probably the best place to find technical assistance for plugins.

        ·   Reply

  9. Rob Robinson

    We also had a problem with out NPAPI plugin not working in Firefox 22. Turns out we had an attribute (hidden=”true”) on the embed tag for our plugin. Removing this attribute allowed Firefox to recognize the plugin again.

      ·   Reply

    1. Alberto López

      Same problem here.
      I have solved it removing “hidden=true” and using “style=visibility:hidden”.

        ·   Reply

      1. Thirilog

        Thank you!
        You saved my life!!

          ·   Reply

    2. Ioan-Cosmin Szanto

      This also happens with our NPAPI plugin and with the VLC plugin,

        ·   Reply

  10. Steve Tapp

    It looks like the Citrix client is broken again but in a different way than V21. Options? Our campus must have this working…

      ·   Reply

    1. Jorge Villalobos Author

      Have you contacted Citrix about this?

        ·   Reply

  11. Charlie Howard

    Our “foofaid.xpi” addon stopped working with FF22 but still works with FF21. This website only is used by a handful of people who are preparing books for Project Gutenberg, so in the grand scheme of things, this is of no importance. But it will impact our productivity, so some of us will have to stay with FF21.

    Nothing in the FF changelog seems obviously relevant to our implementation.

      ·   Reply

    1. Jorge Villalobos Author

      Are you the developer? How did it stop working, do you see any errors in the Error Console?

        ·   Reply

  12. Martin

    You mention that there will be an automatic compatibility validation carried out on all add-ons listed on your website. My company developed an add-on that is not published, thus only used internally. Is there a way to run this automatic compatibility validation on non-published add-ons too?

    Actually with version 22 this add-on stopped working and I am wondering whether this compatibility validation could give more information about the reasons.

      ·   Reply

    1. Jorge Villalobos Author

      We can’t run this validation for external add-ons, but you can run your files through the standalone validator: https://addons.mozilla.org/en-US/developers/addon/validate. You can also get the sources from Github and run it from the command line.

        ·   Reply

  13. Nikhil

    Hi Jorge Villalobos
    My plugin was working fine till firefox 22.
    It is currently giving error
    Components.classes[cid] is undefined..

      ·   Reply

  14. Tim Robinson

    I also have a plugin that uses NPAPI. It worked fine on firefox 21 but doesn’t work on 22. Haven’t got to the bottom of it yet.

    I’m getting increasingly frustrated at the lack of change control being exercised by the Firefox developers – our IE plugin has worked for over 6 years without being even recompiled and the chrome one has worked just about unchanged too, but with firefox it seems every version has more breaking changes :-(

      ·   Reply

  15. jonathan

    FF 22 is not compatible with the latest version of Quicktime. In order to restore sound from QT files, we have to use a legacy version, 21 or earlier. We’ve tried several suggestions posted on the following forum, all unsuccessful.

      ·   Reply

  16. Ray

    Looks like Camelizer is broken with Firefox 22.0.

      ·   Reply

  17. tony 123

    Downloadhelper 4.9.15 won’t work with Firefox22 – I get a greyed out icon but doesn’t work when on youtube or other sites..It worked perfectly in the previous version.
    Can anyone help many thanks

      ·   Reply

  18. tony 123

    It has now began to work normally !! Let’s help the problem its cured and will work correctly all the while.

      ·   Reply

  19. Sunil

    Hi Jorge Villalobos,
    I have downloaded the latest gecko-sdk for firefox 22
    But it is missing xpidl.exe file which should be in “bin” directory.
    Thats why Im unable to build my code with latest gecko-sdk.
    Please help me with this.

      ·   Reply

    1. Jorge Villalobos Author

      There should be an equivalent python file that you can use to build the XPTs. Alternatively you can use the exe of a previous SDK.

        ·   Reply

  20. Shalini Kuruvath

    Selenium ide is not compatible with firefox 23.0.1.

    I am not able to see selenium ide option in the menu even after installing Selenium Expert (Selenium IDE) 0.25 .

    Please look into this.

      ·   Reply

  21. James Edwards

    Now that nsIGlobalHistory2::addURI is no longer available, how do you add a URL to the history?

    The validator simply says “see mozIAsyncHistory for alternative functions”, however that interface doesn’t have a comparable function — updatePlaces only works for URLs which are bookmarked or have already been visited.

      ·   Reply

    1. Jorge Villalobos Author

      Do you get an error if you try to add a URL that isn’t in the history already? There must be a way to add new entries, since Firefox code uses the same interfaces.

        ·   Reply

Post Your Comment