I wrote: > I wrote: >> I've been setting browser.display.screen_resolution to 40 in my >> application since the pages end up being displayed on TVs. In >> Mozilla 1.7, Firefox 1.0 and Firefox 1.5 this change doesn't seem >> to affect font sizes but in XULRunner 1.8 it does.
However, I have verified that in Mozilla 1.7 36 pt and 20 px text are the same size with this setting, as they should be. > ...and the really funny thing is that it works the wrong way. With > a nominal screen resolution of 40, text probably ought to be smaller > _in pixels_ than normal. With a nominal screen resolution of 160, > text ought to be larger _in pixels_. In fact, XULRunner 1.8.0.5 > is scaling fonts the other way! > > A comparison of nsDeviceContextGTK.cpp between Mozilla 1.7 and 1.8 > shows that it's now looking at layout.css.dpi instead; presumably > this resulted in two different scaling mechanisms interfering! > Why the duplication? Further investigation shows this is actually due to a renaming in version 1.8.1, which doesn't yet affect me. What I find in 1.8.0.5 is this: - font sizes specified in pixels are scaled according to the nominal screen resolution as if 1 px means 1/96 inch - font sizes specified in point sizes are scaled according to a fixed screen resolution of 96 dpi This is clearly backwards! What the (expletive deleted) is going on and how can I get the correct behaviour? Ben. -- Ben Hutchings -- [EMAIL PROTECTED] shortened to [EMAIL PROTECTED] If you've signed my GPG key, please send a signature on and to the new uid. You can't have everything. Where would you put it? _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
