Closed
Bug 79337
Opened 24 years ago
Closed 15 years ago
let user overide system fonts
Categories
(SeaMonkey :: Themes, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: ckf.bbs, Unassigned)
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
BuildID: Gecko/20010505
P.S. Dunno why The Bugzilla doesn't accept my email address when using Mozilla
0.9, so I have to use IE5.5 -_-
My perious browser was Mozilla 0.8.0, it ignores the font settings in my
Windows and uses "Tahoma" as the fonts for the title bars, menus and bookmarks
etc, and everything looks great.
But when i upgraded to Mozilla 0.9, It inherits the font settings from my
Windows for those stuffs instead. Since I'm using a Chinese edition of Windows
2000, The fonts now become strange and hard to see.
Reproducible: Always
Steps to Reproduce:
1.Launch Mozilla
2.
3.
Expected Results: I hope Mozilla should allow users to change the fonts for
the Bookmarks and the menu bars...etc.
Morever, now we can only select the font size from the scroll menu inside the
Preference menu. It would be much better if we can type in the font size we
want, that is absent from the scroll menu.
And, before I can select Tahoma for the font of Traditional Chinese language,
but now I can't do that anymore. It's probably not a bug, but I hope that I can
select any fonts for any languages, without restrictions.
Comment 1•24 years ago
|
||
so this is an rfe for letting the user overide system fonts for mozilla, correct?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: A few problems related to fonts → let user overide system fonts
hm... I am also suffering by this problem.
IMHO at least fix the modern theme so that fonts shown on status bar,
and widgets on the mail/news window (like get mail, file...) won't
be so terrible ugly.
btw, font for the toolbars (file, edit, view...), bookmarks and preferences
box are OK.
Comment 3•23 years ago
|
||
->apps
Assignee: asa → pchen
Component: Browser-General → XP Apps
QA Contact: doronr → sairuh
Comment 4•23 years ago
|
||
er, not sure this belongs here. themes? style system? prefs? punt as needed!
Assignee: pchen → hewitt
Component: XP Apps → Themes
QA Contact: sairuh → pmac
Updated•23 years ago
|
Priority: -- → P5
Target Milestone: --- → Future
Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
Updated•17 years ago
|
Assignee: hewitt → nobody
Priority: P5 → --
QA Contact: pmac → themes
Target Milestone: Future → ---
![]() |
||
Comment 5•16 years ago
|
||
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
![]() |
||
Comment 6•16 years ago
|
||
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
![]() |
||
Comment 7•16 years ago
|
||
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
![]() |
||
Comment 8•16 years ago
|
||
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
![]() |
||
Comment 9•16 years ago
|
||
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
![]() |
||
Comment 10•15 years ago
|
||
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: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•