Closed Bug 109830 Opened 23 years ago Closed 23 years ago

Setting Preferences DPI affects chrome's text size.

Categories

(SeaMonkey :: Themes, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bugs, Assigned: hewitt)

References

Details

This bug ties the DPI setting of the document on screen to the theme's own fonts, which should stick with the size GNOME is telling it to use. On my 1400x1050-odd display, if I set the DPI to 72, everything (and I mean everything, from document to any new windows) is too small. If I set the DPI to 96, the document is readable on all fonts and sizes, but theme elements (anything that needs text in the status bar, menu bar, button bar, and URL bar) is too large and chews up real estate. The only compromize is setting it to "system", which is about 92 dpi, but small fonts off of http://www.cyanthan.net (especially in the LiveJournal floating frame) are too small and require bumping up. Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.5) Gecko/20011012 A good solution may be to seperate "theme DPI" from "webpage DPI", and fold this into an "advanced screen settings" dialog box, fixing bug 83060 and bug 83061 at the same time. BTW -- don't assign this to Gerv. He doesn't like these types of bugs because somehow he thinks he knows how to convince an X server what screen DPI it should report (and he better report how he found out, if that is true).
Depends on: 83061
Depends on: 83060
Depends on: 53098
"dpi" is a setting that is logically tied to the monitor. It cannot change between the webpage and chrome. Set it to either "system default" (what the X s erver belives is the dpi) or to the real value of your monitor. What you want is an ugly hack around another problem, probably that the webpage's fonts are displayed too small. There are several ways to fix it, depending on what is the cause. An example is a minimum font size, which is already somewhat implemented in Mozilla, via a backend pref. WONTFIX
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Summary: Setting Preferences DPI affects theme's text size. → Setting Preferences DPI affects chrome's text size.
Ok, since you obviously know about these things, but aren't willing to tell the unwashed masses, list all the ways I can fix this before having to resort to the "ugly hack" which would benifit more than one user, from the three bugs I have in the dependencies. BTW -- Tech support comes with the job of programming. BUG REOPENED.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Oh, BTW, I'm running Slackware 8 on a AMD K6-2 box with 256 megs of memory and XFree 4.1.0
<http://www.mozilla.org/unix/customizing.html>. E.g. // Don't ever show me a font smaller than this: see bug 30910. // This is the new cross-platform pref; the old Unix-only // font.min-size pref is deprecated and will be removed soon. // There may eventually be some related UI, from bug 61883. user_pref("font.minimum-size.x-western", 13); Works?
The correct fix is properly seting your DPI. Break out a ruler, measure your monitor, divide by the desolution. EG: i'm running 1152x864... my monitor is 10.75" vertically. 864/10.75 = 80.3 DPI So I start X with: xinit -- :0 -dpi 80 and all my font problems went away... well, most of them. The others are due to Linux's just shipping with crappy fonts. I don't know how to set the DPI in the conf file, unfortunatly, but you can probably add the -dpi 80 to your startx script.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → INVALID
Confirmed. The latter (telling X what DPI it is at) works better (135 dpi, oui. I need a better monitor). We may need to document this one just incase.
Status: RESOLVED → VERIFIED
Related bugs: - Bug 45838 - Bug 53098 - Bug 119824
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.