211686 - display dpi settings have no influence an CSS font sizes

Status: RESOLVED EXPIRED

(Core Graveyard :: GFX: Gtk, defect)

Description

[Christian Forster]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

Is I set the DPI of the Display ibn Edit->Preferences->Appearance-Fonts, normal
fonts do change. But if a CSS-styled size is displayd in which font-sizes are
given in pt, these setting have no effekt.

The CSS Page is always displayed the same way. Unfortunately if I use
xft-mozilla, the displayed default size (8pt...12pt) are too small to be
readable and this is the only way to set permanent a kind of text zoom.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Felix Miata]

DPI change in prefs is not effective until you shut down Mozilla entirely and
restart. The font size settings in prefs have no impact on page text sized via
CSS absolute sized units, such as pt and px.  Page text sized in pt is larger
when DPI is increased, but unaffected when sized in px. c.f. bug 203000. See
also bug 186718 & bug 206975.

Comment 2

[Christian Forster]

After some retesting the thing appears only to happen with mozilla build with
xft-font-support. Which seems to introduce some other weirdness concerning
dpi-settings.

Comment 3

[Christopher Blizzard (:blizzard)]

Strange, this stuff should work.  Are you building with gtk2 as well?

Comment 4

[Christian Forster]

My first build was without gtk2. These lead to some ugly font rendering in
comparison to kde3 or some gtk2 app. A gtk2 build showed better font rendering,
but the problem with the sizes still exists.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.