As near as I can tell, the upgrade changed the default font size from the user's default size (I don't know for sure that that was the original size) to small: > body, td, th, input { /* redundant rules for bad browsers */ > font-family: verdana, sans-serif; > font-size: small; > } I have my browser's default font sizes set the way they are because I find text at the default sizes to be pleasantly readable. Smaller text is less readable, and in some cases (e.g., an otherwise-unstyled <code/> element, as demonstrated on <https://bugzilla.mozilla.org/describecomponents.cgi?product=Bugzilla>) the text borders on illegibility. I consider this to be an accessibility issue with b.m.o. The original updated skin for Devmo (MDC) had a problem similar to this in that the default font size was smaller than the user's set size; I did some arguing and got it changed to 1.0em. We recently had one person posting to Devmo's mailing list who explicitly thanked us for using a good text size: http://mail.mozilla.org/pipermail/devmo-general/2005-October/000429.html Note also that this problem is likely what caused bug 313488 - if I use the DOM Inspector to remove |font-family: small| from the body element that problem goes away.

bug 313461?

(In reply to comment #1) > bug 313461? That's just one instance of this (a "sub-bug", I guess), and it looks like it's fixable by fixing bug 313450 (removing the line that causes that bug fixes bug 313461 as well). One place I've discovered where this is particularly noticeable is in the patch viewer. The patch text is definitely at the lower bounds of readability (and just to be clear about it, I *don't* have poor vision): https://bugzilla.mozilla.org/attachment.cgi?id=200483&action=diff

(In reply to comment #2) > it looks like it's fixable by fixing bug 313450 (removing the line that causes > that bug fixes bug 313461 as well). (To be clear, this would just change the text from being small-small to just small. To get rid of the last small we have to do something about it here.)

I don't plan to work on these at this point because the broader focus is now on trying to upgrade to Bugzilla 2.22, and it'll all have to be redone anyway to fit the 2.22 templates. But if someone else wants to show me what to patch on any of these I'll be happy to patch the current install between now and then.

This isn't wontfix as in I don't want to fix it, it's a wontfix as in no longer relevant. We're upgrading to a new version of Bugzilla in the next week, and it has a completely new skin. If this is still a problem after the upgrade, please file a new bug. sgarrity is planning on doing some customization of the bmo skin beyond what we're doing in the upgrade probably in late January, and it can get taken into account then.