maemo.org Bugzilla – Bug 1296
text size too small, does not respect user settings
Last modified: 2007-12-04 12:52:15 UTC
You need to log in before you can comment on or make changes to this bug.
maemo.org css seems to have been tweaked between 5th and 6th of May: Some texts are just very small and some no longer respect my browsers font size setting. This is evident in bugzilla (the comment bodies are too small and do not scale with my font size setting) and front page (Announcement and News items are too small). Neil MacLeod comments in bug 1293: "Just so you know, the monospaced font size currently used when viewing the bug detail is waaay too small in Firefox 2.0.0.3 on XP (Normal text size). The same bug detail looks OK in IE 7." My browser string: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty)
Created an attachment (id=411) [details] screenshot of bugzilla
(From update of attachment 411 [details]) Font size set to an exaggerated value of 24 to emphasize the problem
Everything looks pretty good now, AFAICS. the bugzilla comment bodies still do not respect the default font size setting in Firefox, so someone with poor eyesight might still complain...
I will look at the font sizes in the bugzilla comments. Thanks for the report Jussi!
I have no win xp, but tested the comments on win2k using FF 2.0.0.3. If i increase the text size then all font sizes increase, including the comments. So I wonder what to do now...
(In reply to comment #5) > I have no win xp, but tested the comments on win2k using FF 2.0.0.3. If i > increase the text size then all font sizes increase, including the comments. > So I wonder what to do now... No XP here either but if you are referring to my last comment, I was talking about the _default_ font size (the one set in browser preferences). Increasing the size with ctrl-+ works fine, but for some reason the default font size does not affect the comment bodies (although it does affect all other text, see the attachment for example).
I just checked and bugzilla.mozilla.org does the same thing... I suggest you close this as fixed (based on the frontpage fix) or wontfix (as it's really not that important).
Marking fixed as per bug comments
Closing RESOLVED and FIX bugs. If error/problem still occurs, please reopen bug with proper comments.