Closed Bug 119824 Opened 23 years ago Closed 14 years ago

Chrome text tends to be drawn at wrong size at varying DPI settings

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED
Future

People

(Reporter: bugmail, Assigned: jag+mozilla)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.7+) Gecko/20020111
BuildID:    2002011108

Text in chrome tends to draw at unusual sizes if the Display Resolution setting
is anything other than the offered defaults of 72 or 96.

This behavior only occurs when only one user profile exists.

Reproducible: Always
Steps to Reproduce:
1. Edit prefs.js and change display resolution to 97
2. Start up Mozilla

Actual Results:  Text in the Personal Toolbar is drawn approximately one point
size smaller than normal. Text on the status bar may or may not be drawn one
size smaller than normal. Text in Mail/News may be drawn one size smaller than
normal.

Expected Results:  Chrome text should draw at the same resolution regardless of
the specified Display Resolution.

In my testing, I saw no problems setting DPI to 71.

Setting to 73 caused Personal Toolbar text to be drawn one size smaller.

Setting to 95 caused the Status Bar text to be one size smaller.
Note: this problem also occurs in Fizzilla.

This bug is a follow-on to bug 88485.
->jaggernaut
Assignee: trudelle → jaggernaut
-> Future
Target Milestone: --- → Future
Severity: trivial → minor
Blocks: 134942
Related to bug 45838?
Related bugs:
- Bug 45838
- Bug 53098
- Bug 109830
Setting OS to Mac OS X per comment 4.
OS: Mac System 9.x → MacOS X
Product: Core → Mozilla Application Suite
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: