Toolkit made various changes to about: pages within the scope of their "Chameleon" (bug 1097111), mostly mimicking Windows 8-10 appearance. Those are not going well with the SeaMonkey styles at all (bug 1192276). It is my understanding that bug 1189918 and bug 1190465 now enables us to fork those style pages without harming theme developers, thus is should be done. This specific bug is for reverting the major changes in the about:addons page and its tabs, reverting general style changes made (fonts, including the fixed size apparently designed for high-resolution screens; button and selector styling; icons), preferably without the need to also fork the underlying page itself.

About:addons has huge rows, and lacks version numbers in the list pane, apparently catering to those users (kindergarten kiddies?) for whom five add-ons is "many" and version numbers are Sanskrit (or maybe Cherokee script, if Hindi is your mother language) :-/ ; but the "Slim Add-ons Manager" and "Add-ons Manager - Version Number" add-ons go a long way toward fixing that. Then there is also userContent.css. But apart from that, isn't the default theme "ugly beyond fixing"? The only circumstance when it cannot be avoided is when in Safe Mode, and (as long as bsmedberg and kev don't "fix" bug 1222546), there are many better themes (including Modern if you don't want to enhance it with a lightweight theme) to choose from for when you aren't in Safe Mode. Anyway, if you want to fix this and related bugs, I guess that that theme has become so generally ugly that any change could only be for the better anyway. I wonder how new users of Firefox can put up with it.

(In reply to Tony Mechelynck [:tonymec] from comment #1) > About:addons has huge rows, and lacks version numbers in the list pane, Re the version numbers, that's more than just a theme change. As far as I know, it's a binding which was removed by the Firefox developers. But then, a binding can be added back in a CSS file, and just the missing code added in a separate XML file if necessary. This may not be within the scope of this specific bug report, but if the binding itself is still around and it is fixable by just adding it back in the CSS part, that could (and should) certainly be done here. > But apart from that, isn't the default theme "ugly beyond fixing"? > bsmedberg and kev don't "fix" bug 1222546 The fact that they want to get rid of "real" themes altogether should be enough motivation to work on making SeaMonkey's shipped themes better. > I wonder how new users of Firefox can put up with it. :-) actually, personally I think that SeaMonkey's default (classic) theme looks quite decent with the Windows Classic desktop theme, and it's fairly ok on KDE4 (I like modern there better).

Can someone do a screen grab for the addons manager pre-Chameleon or even pre-Australis :P