Closed
Bug 233357
Opened 20 years ago
Closed 19 years ago
Sometimes scrolling leads to incorrect display of text
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: c, Unassigned)
References
Details
Attachments
(1 file)
6.52 KB,
image/png
|
Details |
User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 Text display sometimes not correct. See screenshot. Reproducible: Sometimes Steps to Reproduce: Rather irrational. Not clear when it happens.
Reporter | ||
Comment 1•20 years ago
|
||
Reporter | ||
Comment 3•20 years ago
|
||
(In reply to comment #2) > What is your "display resolution" set to in preferences->fonts ? Fonts for Western: Proportional: Serif size 16 Monospace: adobe-courier-iso8859-1 size 12 Minimum font size: none Display resolution: System setting (Gimp preferences tell me that Monitor Resolution from Windowing System is 100x100) System is debian sarge.
Does the bug only appear in Mailnews? Does it persist if you change resolution in prefs to 96? (Stop/start mozilla after changing that setting before you test it)
Reporter | ||
Comment 5•20 years ago
|
||
(In reply to comment #4) > Does the bug only appear in Mailnews? > Does it persist if you change resolution in prefs to 96? > (Stop/start mozilla after changing that setting before you test it) It does appear only with Display == System Setting and only in lines which contain a smiley and no Reply separator at the beginning of the line (!!). Can't tell about Browser component, because no smileys there.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Comment 7•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 8•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•