Red Hat Bugzilla – Bug 439616
Firefox is HUGE after default install.
Last modified: 2008-04-01 10:07:34 EDT
Description of problem:
After installing a fresh copy of Rawhide on my machine, Firefox appears to be
magnified about 500% despite View -> Zoom being "reset" many times. I am at the
default DPI of 111.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install rawhide.
2. Enter Gnome
3. Start Firefox
Gigantic Firefox. :-)
Normal looking Firefox
Radeon R350 Chipset. Dell 2007FP x2 (no dual head set up yet though).
Created attachment 299584 [details]
Screenshot of huge Firefox.
Actually I just noticed that the screenshot says I'm running at 1900x1200
although I *should* be running at 1600x1200 (and this is what the display
configuration claims I am running at).
I have a feeling this may be part of the problem. So perhaps this is misfiled.
Will update shortly.
Resolved my resolution issues with xrandr. Firefox
is still huge! Any ideas? Will upload new
Created attachment 299589 [details]
Resolution issues resolved.
Oddly enough, page text also looks huge in Galeon, but everything looks normal
in Konqueror. Could this be a Gnome issue?
Galeon uses gecko. Every rendering bug in gecko will be seen in galeon and
I also found this:
Perhaps this is what is causing my problem. Huge font problems in Gecko-based
browsers go away when I switch to the vesa driver.
Feel free to close this unless you think Gecko may still be at fault in some
way? I will reopen if needed.
I thought I pasted this link the last time.
Thanks Christopher, I'll follow upstream on this.
We believe that it is more appropriate to let this bug to be resolved upstream.
Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.
Thank you for the bug report.
Just to add a workaround from the upstream bug -- set layout.css.dpi in
about:config to 96. It should work then.
As I'm sure you are aware (but for the benefit of anyone else stumbling across
this), looks as though upstream has fixed the bug:
Hopefully this will show up soon in rawhide.