by Dagger (Developer) on Nov. 25, 2015 · permalink

It was less for vanity and more so that the buttons don't take up over half the dialog. It looks like this with the buttons enabled: https://i.imgur.com/zjQ3hGV.png.

I intend to add options to this when I rewrite it, but I have so much other crap to fix in Firefox that I haven't managed to get to that yet. In the meantime, you should still be able to use right-click -> Remove, double-click -> Remove, or this in Stylish:

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);
@-moz-document url(about:addons) {
.addon button.remove { display: inherit !important; }
}

by Dagger (Developer) on Aug. 13, 2015 · permalink

Yeah, it's very broken, sorry. I just uploaded a new version that fixes the biggest issue (the blank window), but Mozilla also landed the in-content theme for about:addons in Fx40, which totally screws up the styling, and I just haven't had the motivation to do anything about that yet.

(It's a bit of a pain to fix, because I basically need to rewrite the extension, and Australis pretty much killed all my enthusiasm for upgrading off of 3.6, so I've just been using 3.6+28.0 since then, so the horrible about:addons styling hasn't been bothering me so much. I do intend to update this extension, because I'll need to upgrade at /some/ point, but it just hasn't happened yet.)

by Dagger (Developer) on April 14, 2015 · permalink

That's actually deliberate. There's less space in a small dialog than in a full-screen window, it starts to look kinda busy with Disable/Enable and Remove for every single extension, and how often do you remove extensions anyway?

You can use the context menu, or double-click to open the full details page and use the Remove button there. Or if you really want Remove buttons in the main listing, use this in Stylish:

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);
@-moz-document url(about:addons) {
.addon button.remove { display: inherit !important; }
}

Edit: Hey, did you know that AMO doesn't email me when reviews are edited? Yes, that's a fair opinion. I'm going to have to rewrite the whole extension to handle all the breakage in Fx40, so I'll see what I can do about these buttons while I'm at it. (It'll have to be an option of some kind, because I still think 3-4 buttons for every single extension is a bit too much.)

by Dagger (Developer) on Dec. 11, 2013 · permalink

An attribute makes a lot of sense; I'll add that.

I looked at the "width: 4.5em" rule... and it looks like it's completely unnecessary. It renders exactly the same without it, even back in Firefox 5.0. Which means I need to work out why it was there in the first place...

(I also need to work out how to handle the CtP plugin setting UI, which has been semi-broken for far too long, so it's going to take me a few days to upload a new version, plus however long it takes to get reviewed after that.)

by Dagger (Developer) on Nov. 4, 2013 · permalink

It actually seems to work okay(ish) together with Cleanest Addon Manager. You can use this CSS with Stylish to patch up some of the odd bits: https://pastebin.mozilla.org/3422457

I'll have to do a bit of thinking if I want to ship that CSS by default, since I'd like to avoid just blindly adding !important rules to patch over other !important rules.

by Dagger (Developer) on Nov. 9, 2011 · permalink

It looks like this is caused by the 'document.getElementById("categories");' at the bottom of change_default_view.xul. With that line, Greasemonkey decides not to add itself to the list. Without that line, if you close the AM with the search tab selected, it loads addons://updates/available rather than the default tab. Bizarre. (That line isn't even supposed to do anything!)

I will try and fix this properly, but for now the workarounds are either to pick "Manage User Scripts" from the GM menu/toolbar icon, or to use Scriptish instead.