Skip to content

Firefox 4 Add-on Compatibility presentation

I’m presenting about Firefox 4 Add-on Compatibility at the Mozilla Summit a little later today. Here are the slides in PDF version for all of those interested.

Firefox 4 for Add-on Developers

For now, this is a pretty good reference if you want to start supporting the Firefox 4 betas in your add-ons. I’ll be elaborating on this subject through the following weeks, in the Add-ons Blog.

{ 3 } Comments

  1. Wladimir Palant | 2010/07/07 at 12:47 PM | Permalink

    Thank you! I will be attending a different presentation so skimming through your slides really helped.

  2. Mook | 2010/07/08 at 3:00 AM | Permalink

    Hmm, reading it now that it’s all in one place, random thoughts… but I realize that they probably shouldn’t all go to you, of course. Where should I be sticking them? m.d.plat?

    - Since XPCOM registration is now static, it’s now not possible to do the old “look up the old cid before clobbering the contract id registration with your own” trick to forward things to the previous implementation, correct? (Was going to suggest somebody wrap mozIPersonalDictionary earlier, but realized that wouldn’t work. oops.)
    - Remote xul also includes remote xbl! You need to mention that. (bug 546857 comment 31)
    - How far does disabling remote xul reach? Anything that doesn’t currently have access to Components.classes will have no access to xul? resource:// and file:// things won’t have it either, then? (Just wanted to confirm that.)
    - The status bar changes are, as far as I know, _way_ too unclear at this point. I may be wrong, but I haven’t seen anything actually concrete yet… :)
    - Surprised there’s no mention of the new devtools (console, inspector). The per-tab nature of console at least would be interesting.

    Thanks for rounding things up so it’s easier to complain about ;)

  3. jorge | 2010/07/08 at 4:56 PM | Permalink

    @Mook:
    - XPCOM. My guess is that overriding component implementations should be easier now with the chrome registration, since what you’re doing are kind of like overlays. Maybe I’m missing something, though, I admit I’ve rarely had to do that. You should discuss this at the plat newsgroup, or maybe directly with Mossop.
    - Remote XUL. That would be only XUL served through HTTP. file and resource URLs should continue to work, as far as I know. And yes, that includes XBL.
    - Status bar. I haven’t seen anything concrete either, but it looks like it’s even more real than I thought :/. Expect more posts on planet about it.
    - New dev tools. Those look nice, and I forgot about them to be honest. That last tab with “new stuff” is just to balance out the presentation a little bit, so I give it too much attention.

Post a Comment

Your email is never published nor shared. Required fields are marked *