Bug 329045 made several changes to the Extension Manager that should be reviewed in order to be sure that it is doing the right things in regards to accessibility. The obvious changes that need to be reviewed are extensions.xul (the radiogroup that is based on the pref panel buttons) and extensions.xml (the addonsmessage which is based on browsermessage). cc'ing aaronlev and Mark Pilgrim

access key word?

While trying to reproduce bug 335747 I've noted that Console²'s FAYT implementation (which might eventually end up in Toolkit through bug 298371) for <richlistbox> doesn't work any longer. That implementation depends on the label property of <richlistitem> which for add-ons now always returns an empty string because of the heavy use of inner bindings. To resolve this, #addon-base or any binding inheriting from it should reimplement the label property, returning at least name and version (and possibly description and installation state) of the add-on. I'm not sure though, whether the label property is used elsewhere...

It would probably be best to utilize the fayt_label for the EM as in your patch or what ever method gets implemented as the next rev of richlistbox.

The add-ons window also uses <prefpane> and therefore triggers bug 334370.

(In reply to comment #2) > To resolve this, #addon-base or any binding inheriting from it should > reimplement the label property, returning at least name and version (and > possibly description and installation state) of the add-on. I believe this is the same bug that I independently found and logged as bug 338048.

--> blocking beta2

Mark, I'm putting this on your list for now, since the active dependencies are both assigned to you.

Dependencies are on the blocker list, pulling this off (no meta bugs!)