Closed
Bug 354505
Opened 19 years ago
Closed 19 years ago
Firefox's GNOME support should use GNOME's font DPI value
Categories
(Core Graveyard :: GFX: Gtk, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 323962
People
(Reporter: sfllaw, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5
From https://launchpad.net/distros/ubuntu/+source/firefox/+bug/19524
Firefox has support for some GNOME integration. As part of this, it should be possible for Firefox to fall back on the font DPI setting stored inside GConf at /desktop/gnome/font_rendering/dpi. This defaults to 96, which is what Firefox does as well, but if that's changed then Firefox should change correspondingly.
Reproducible: Always
Steps to Reproduce:
1. Fire up a GNOME desktop.
2. Go into Preferences > Font > Details. Set the font DPI to 120.
3. Open Firefox.
Actual Results:
Firefox keeps its own font DPI setting.
Expected Results:
Firefox sees that GNOME's DPI is at 120 and that it doesn't have an overriding value in layout.css.dpi. It renders assuming the screen is at 120 DPI.
Comment 1•19 years ago
|
||
What's your buildconfig look like? As far as I can tell we try to use that setting as long as it's set: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/gfx/src/gtk/nsDeviceContextGTK.cpp&rev=1.131&mark=1052-1072#1047
Can you grab the firefox-dbg package and maybe step through that function to see what's going on?
Component: OS Integration → GFX: Gtk
Product: Firefox → Core
QA Contact: os.integration → gtk
Version: unspecified → 1.8 Branch
Comment 2•19 years ago
|
||
already fixed for FF2
*** This bug has been marked as a duplicate of 323962 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•