Extension Developers – More On Updating

We have been putting out the call for extension developers to start the process of updating their extension to workin Firefox 3. It’s never fun when your extension breaks because of changes in Firefox, but everyone wants to make the platform better. In doing so, we had to break some eggs.

On the bright side, extension developers seem to be really charging ahead full steam. In addition to finding signs of extension update work being done on developer websites, #extdev on Mozilla IRC has been pretty active. I have also noticed posts on Mozillazine forums too.

I thought I’d list a few issues I have seen come up during update discussions:

  • event.preventBubble() has been removed in Firefox 3. It was deprecated in Firefox 2 and code should be using event.stopPropagation(), which also works in Firefox 2.
  • Using window.addEventListener("load", myFunc, true) to listen for web content page loads does not work anymore. Changes were made to improve security and this was fallout from those changes. You should be using gBrowser.addEventListener("load", myFunc, true) anyway. Listening for “load” events on the Firefox main window is a bit overkill. Listening for the event on the tabbed browser makes more sense and works (in Firefox 2 as well).
  • The XUL popup system (popup, menupopup & tooltip) has been significantly overhauled in Firefox 3. Some methods were deprecated (showPopup), some were added (openPopup & openPopupAtScreen) and a whole new type of popup was added (panel). See the new Popup Guide for more information.

There is a wiki page listing a bunch of stuff extension developers should consider or to watch when updating. If you find something, add it to the list.

One of the other benefits of updating early is the potential for helping us find Firefox bugs. We recently had an extension fail to update to Firefox 3 for no apparent reason. It was doing nothing different than when running in Firefox 2 and didn’t seem to hit any of the other know update issues.

Turns out, the extension adds a utility method to the Array prototype which worked fine in Firefox 2, but caused weird exceptions in Firefox 3. The exception ocurred in places where Firefox 3 added uses of for each on Arrays, which is a no-no. The problem didn’t show up in any tests because Firefox 3 doesn’t add anything to the Array prototype. We are fixing this in Firefox, but it could happen to other extensions if they use for each on Arrays. Perhaps the best advice is to always be defensive when dealing with things that could pollute the global namespace – shared by Firefox and all of its extensions.

4 Comments

  1. dafi said,

    January 18, 2008 @ 1:49 am

    The dark side of FF3 is XBL, my extension stops to work from FF3 b2 (where it works) and FF3 b3pre.
    Nobody helped me, my last help request on Mozillazine
    http://forums.mozillazine.org/viewtopic.php?p=3215879&sid=4e0e1ba37a4046e8b8c5a5344baf956b

    IMHO Firefox developers should describe why XBL no more works on content window.
    The bug https://bugzilla.mozilla.org/show_bug.cgi?id=236839 is already open and its impact became intolerable for deeply XBL based extensions.

    I know my extension isn’t important but why I must stop its development if I like it (I’m the author ;-) ) and I have many users.

  2. AndyTap said,

    January 24, 2008 @ 9:01 am

    Is Firefox can support locate a element by mouse pointer like IE developer toolbar?

  3. shaver » why update add-ons now? said,

    January 24, 2008 @ 9:47 am

    […] Firefox 3 still a couple of months away, it would seem reasonable to wonder why we’re encouraging add-on developers to get their add-ons updated for Firefox 3 already. For most add-on developers, it will indeed be a […]

  4. foxiewire.com said,

    January 29, 2008 @ 12:27 pm

    Mark Finkle‚Äôs Weblog: Extension Developers – More On Updating…

    Mark Finkle writes, "We have been putting out the call for extension developers to start the process of updating their extension to work in Firefox 3. It’s never fun when your extension breaks because of changes in Firefox, but everyone wants to …

RSS feed for comments on this post