Closed Bug 886732 Opened 11 years ago Closed 8 years ago

mail window fonts and spacing change after SeaMonkey upgrade to 2.19


(SeaMonkey :: General, defect)

SeaMonkey 2.19 Branch
Not set


(Not tracked)



(Reporter: zetka, Unassigned)





(2 files)

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19 (Beta/Release)
Build ID: 20130619213447

Steps to reproduce:

upgraded to SM 2.19

Actual results:

display change of the mail window -different line spacing. I was not able to change this parameters, the CTRL+ (-) works only for message sub-window, not for the main window with email list or with branch of the Inbox. I have default window font size on 125%.

Expected results:

The setting for fonts, line spacing even for the main mail window should be settable and not being changed after SM update.
> upgraded to SM 2.19

What did you upgrade from?
And can you provide a screenshot of incorrectly displayed window?
Whiteboard: closeme INCO 2013-07-15
I think I have upgraded from 2.17 or 2.18?, I have automatic upgrage setting. Attached is main window. The inter-line spacing is different than before and the icons seems "blury".
Open about:config, find layout.css.devPixelsPerPx and set it to 1, does it resolves problem for you?
NO, it decreases the size of all fonts in all windows, inclusive the mail window. The size is too small now, the inter-line distance, I have attached the screenshot, how does it seems now. Is there any help how this variables in the SM should be set up?
The icons are now looking normal.
screenshot when  layout.css.devPixelsPerPx set it to 1. My native Windows XP display setting is 120dpi and basi display resolution is 1920x1200pixels.
So, this is expected consequences of Bug 844604, not sure which of Bug 820679 blockers covers your case. Anyway, you can try to find layout.css.devPixelsPerPx value which suits you or revert to -1 wait till this will be fixed in Core.
Almost concurrently, the latest releases for Firefox (22.0) and SeaMonkey (19.0) have radically altered the appearance of web sites (and mail, in the case of SeaMonkey).  Where I previously had userChrome.css files specifying a default font size of 12 pt, now to avoid web pages looking like first grade reading texts with the new releases, I had to reduce that to 8 pt.  But that was just the beginning of needed changes.  I also had to change icon sizes, and adjust the browser tabs line font-size and height to get the chrome looking like previous versions of these browsers.  But I hadn't discovered or figured out how to reduce line spacing in the SeaMonkey mail inbox window from its current approximate 1.5 spacing.

After searching for "SeaMonkey mail inbox line spacing" led me to this bug, I tried changing layout.css.devPixelsPerPx, but nothing helped.  Another result of that search led me to the Mozillazine forum thread "TB 6 inbox email listing looks like 1.5 line spacing ...", and a July 2010 post offered this code snippet:

    listitem, treechildren::-moz-tree-row {
        min-height: 20px !important;

Added to my userChrome.css, with a change to 12px for my 8pt font size, this gave me nicely packed lines in my mail folder & threads listings.  However, the folder lists in Move To or Copy To still have that 1.5 line spacing, but that's easier to live with (though a fix would be most welcome).

The major display changes have been a serious disruption to using either of these Mozilla applications, much more profound than anything I've encountered in the past (from version 1.0 in both).  I strongly considered reverting to the previous versions of both and waiting for FFX 25 & SM 22. I cringe to think of what these changes might mean to someone less familiar with configuration details, which is probably a majority of users.  There also was no mention of such issues in the release notes.
OS: Windows XP → All
Hardware: x86 → All
Whiteboard: closeme INCO 2013-07-15
Same thing happened to me upon upgrading from 2.21 to 2.22
This should be fixed now that Bug 927779 (Windows Classic theme XUL tree cell padding regression} is fixed in 2.23, 2.24, and higher.
Depends on: 927779
Ever confirmed: true
Whiteboard: [CLOSEME 2015-12-31]
Resolved per whiteboard
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [CLOSEME 2015-12-31]
You need to log in before you can comment on or make changes to this bug.