horrible page rendering problems since Firefox 3 beta 4

[sibidiba]

Binary package hint: firefox

Since I upgraded Firefox 3 to beta 4, I permanently experience horrible rendering problems, in particular:

- images are rescaled needless and wrong

- proportions and alignment are wrong

- object are misplaced

- some fonts are near unreadable small

- input objects are huge

The bug does not affect all sites, but all the major ones. I do not experience it, if my external monitor is not connected to my laptop, thus the DPI is detected correctly. Changing the dpi settings in about:config does not have any effect on this!
(DPI is correctly set in Gnome and gdm, xrandr -q displays the right numbers. Altough xdpyinfo returns 209 digit per inch. I have only 98. This may be affected by the fact, that I use a virtual screen with the resolution of 2048x2048).

I attach some screenshots, and marked the main problems.

[sibidiba (sibidiba)]

I'm running Hardy, updated on a daily basis.

[Andrew Keyes (akeyes)]

Looking at your final example (Screenshot-2.png), it appears that Firefox is set to zoom pages a bit. I am able to confirm the Google logo quality that you point out in that image, by zooming in on the page in Firefox. Try reseting your zoom in Firefox by: View -> Zoom -> Reset.

Have you tried changing your dpi in Gnome?
This can be done by going to System -> Preferences -> Appearance -> Fonts -> Details... -> Resolution

[sibidiba (sibidiba)]

Thank you. I could swear I tried that already. Images seem now ok.

But font sizes are still not as before. For example in gmail font sizes are a magnitude smaller then before. It is problematic to read the text on several pages.

[sibidiba (sibidiba)]

Also I still experience the "object misplacement", that is, several objects overlap or aren't there where they were before.

[Andrew Keyes (akeyes)]

I've often run across the object misplacement as you pointed out in Screenshot-1.png, this is often caused by web designers not taking into consideration the width of characters on different systems in their designs.

If you continue to find fonts that are too small, try using the minimum font size setting in Firefox, it can be found by going: Edit -> Preferences -> Content -> (Fonts & Colors) Advanced... -> Minimum font size.

[sibidiba (sibidiba)]

Setting a minimum font size have had no effect.

I did not experience any of the mentioned problems before FF beta4.

[sibidiba (sibidiba)]

Removing

user_pref("font.language.group", "x-central-euro");
user_pref("font.minimum-size.x-central-euro", 0);
user_pref("font.size.fixed.x-central-euro", 16);
user_pref("font.size.variable.x-western", 12);

from prefs.js resolved the "object misplacement" and the issue of the unreadable small fonts.

[Alexander Sack (asac)]

please test if its still the case in latest ffox 3

[DFreeze (dfreeze)]

I'm not sure if this is part of the same bug or if I should file another, but just yesterday I found out that zooming out (i.e. smaller fonts) on my iGoogle page, made the whole page suddenly align to the right. Zooming back in to original or bigger fonts restored the alignment. I could reproduce this behaviour on my other Hardy box, both updated to current. (b.t.w. my iGoogle page has three columns, in case that has any influence...).

[Alexander Sack (asac)]

On Tue, Jun 10, 2008 at 08:21:55AM -0000, Goswin wrote:
> I'm not sure if this is part of the same bug or if I should file
> another, but just yesterday I found out that zooming out (i.e. smaller
> fonts) on my iGoogle page, made the whole page suddenly align to the
> right. Zooming back in to original or bigger fonts restored the
> alignment. I could reproduce this behaviour on my other Hardy box, both
> updated to current. (b.t.w. my iGoogle page has three columns, in case
> that has any influence...).
>

does this still happen with 3.0 RC1 (which should be available in
hardy-updates since yesterday) ?

 - Alexander

[DFreeze (dfreeze)]

Yeah, I checked the Firefox version I used, and it said something like 3.0 (so the 3.0b5 was gone). I assume that's the RC I was running.

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[Alexander Sack (asac)]

On Sat, Nov 29, 2008 at 09:01:40PM -0000, JaysonRowe wrote:
> Since it's been a very long time since any additional info was added to
> this bug, I'm just checking to see if this is still an issue, and find
> out what additional work should be done on this bug.
>

Yes, please close ... this bug is far to unspecific to be of any use.

 - Alexander

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!