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.
...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? 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
