Closed Bug 234826 Opened 22 years ago Closed 21 years ago

GUI does not use windows font if using StyleXP windows theme

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: phil, Assigned: bugzilla)

References

()

Details

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 When using a 3rd party windows visual style using StyleXP, the FireFox GUI defaults to Times New Roman and does not display the current system font. See URL for image. Reproducible: Always Steps to Reproduce: 1. Install StyleXP (if not already installed) http://www.tgtsoft.com/ 2. Change to a non-standard windows theme http://www.themexp.org 3. Open FireFox Browser Actual Results: FireFox uses Times New Roman for GUI text elements in toolbars, menus and dialog boxes. Expected Results: FireFox should display the GUI using the font defined in the current custom visual style.
does StyleXP change the windows fonts or does it use its own API? If it doesn't change the font via the standards windows API, nsITheme will use what the Windows API returns.
QA Contact: mconnor
(In reply to comment #1) > does StyleXP change the windows fonts or does it use its own API? If it doesn't > change the font via the standards windows API, nsITheme will use what the > Windows API returns. I'm not sure, all I know is that FireFox is the only application i've used that doesn't display the visual styles in styleXP fully.
Firefox is a cross-platform app with a frontend written in XUL, not a native Windows app, so it works a little differently. We inherit the base fonts from the native Windows API, but if StyleXP allows for bypassing this API, we don't have a means to overcome this because we don't look for third-party APIs
I don't think we have any intention of supporting non-native desktop environments.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.