Closed Bug 161660 Opened 24 years ago Closed 23 years ago

Mozilla apps corrupt fonts when Windows dpi setting is changed

Categories

(Core :: Layout: Text and Fonts, defect)

Product:
Core
Component:
Layout: Text and Fonts
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: null_pointer_us, Unassigned)

References

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721 BuildID: 2002072104 I recently changed my Windows DPI setting via Display Properties/Advanced Settings, but now Mozilla, Mail, and Composer all tend to display blocky or botched fonts when their windows are scrolled. Reproducible: Sometimes Steps to Reproduce: 1. Open a web page, email message in either Navigator, Composer, or Mail. 2. Scroll the page. 3. The page text becomes garbled and blocky - sometimes. Actual Results: The page displayed incorrectly - the text was all messed up. Expected Results: The scrolling should not cause the fonts to be redrawn incorrectly. The problem only seems to occur with certain fonts at certain sizes; i.e., those fonts whose size is affected by the change in DPI.
This isn't editor....
Assignee: kin → attinasi
Component: Editor: Core → Layout
QA Contact: sujay → petersen
Hmm...after adjusting my Windows dpi setting, I found that the bug only seems to occur when a custom Windows DPI setting is chosen. Setting Windows to large fonts (120 dpi) fails to reproduce the problem. However, setting the dpi to say, 101, via the Windows XP advanced display properties dialog box does cause the problem to occur.
Related to bug 114270?
.
Assignee: attinasi → font
Component: Layout → Layout: Fonts and Text
QA Contact: cpetersen0953 → ian
*** This bug has been marked as a duplicate of 114270 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Not a duplicate. Probably related to the fact that we need to round p2t to an integer on Windows (or did we do that already?).
.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
I suspect this was fixed by the patch in bug 199159 comment 89. Could you retest with a current build (for example, 1.4rc3)?
Depends on: 199159
Yes, it appears to be working fine on 1.4rc3. I'm not sure whether I ought to change the bug status myself or whether the mozilla team is supposed to do that, so I am leaving the status where it is.
Marking fixed, then, since I'm pretty sure we know what fixed it (see comment 8).
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
verifying
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.