Closed
Bug 284970
Opened 20 years ago
Closed 20 years ago
rendering many things--constant movement of one pixel
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: kbolino, Unassigned)
Details
Attachments
(6 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041221 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041221 Platform: Linux (given builds & my own) (i have also experienced this with FreeBSD, NetBSD) Library notes: This problem is more frequent when compiled with libXft (X11/FreeType) but occurs without it as well. Applies to: The rendering of many things--favicons in tabs/bookmarks, inline images, and text What happens: When the page loads, everything is fine. Movement of the mouse over any of the affected things causes them to "jump" one pixel up, down, left, or right. Clicking and selection do this as well. They will periodically jump back to their old positions with add'l mouse movement, scrolling, or window focus changes. Reproducible: Sometimes Steps to Reproduce: 1. Download/make and use a Linux build 2. View any page (mozilla.org is a good example) 3. Move the mouse across images, select text, create tabs, view pages with favicons Actual Results: The items (or portions of them) jump one pixel. Expected Results: The positions should have remained static.
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
| Reporter | ||
Comment 3•20 years ago
|
||
| Reporter | ||
Updated•20 years ago
|
Attachment #176432 -
Attachment description: firefox download before mouseover → firefox download before selection
| Reporter | ||
Comment 4•20 years ago
|
||
| Reporter | ||
Comment 5•20 years ago
|
||
| Reporter | ||
Comment 6•20 years ago
|
||
Updated•20 years ago
|
Version: unspecified → 1.7 Branch
| Reporter | ||
Comment 7•20 years ago
|
||
This "bug" is actually due to the dots-per-inch setting for Font rendering. Setting this away from "System setting" to something more reasonable, like say 96 dpi seems to fix it. This isn't so much a "fix" as it is a work around.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•