Closed
Bug 798362
Opened 12 years ago
Closed 10 years ago
Gecko doesn't apply system default scale on Gtk
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 712898
People
(Reporter: candrews, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/18.0 Firefox/18.0 Build ID: 20121003073751 Steps to reproduce: When Firefox is first loaded (or a clean profile is created) on a high-DPI system (tested under 220 dpi on a Macbook Pro Retina), Firefox does not scale its interface. Everything is absolutely tiny. Steps to Reproduce: 1. Open Firefox under high-DPI system (e.g. set DPI to 250% for a clear demonstration) 2. browse to any page 3. compare to 96 dpi output Actual results: The two sets of output (96 dpi/high-DPI) are identical. Expected results: The high-DPI output should be enlarged according to the DPI.
Note that the equivalent bugs for other platforms are: Mac OS X: bug 674373 Windows: bug 603880
Manually setting the about:config option "layout.css.devPixelsPerPx" to 2 is the workaround I'm currently using.
Comment 3•12 years ago
|
||
When you say "set DPI", exactly which indicator are you changing? Which other GTK apps are scaling their user interfaces when that is changed?
I'm just using my Retina system as-is. xpdyinfo tells me the DPI is 220. For testing, you can set the size of your monitor. This page indicates how to do that, and how to get the current size/resolution/dpi: https://wiki.archlinux.org/index.php/Xorg#Display_Size_and_DPI
Comment 5•12 years ago
|
||
this may be a duplicate of 712898
Comment 6•11 years ago
|
||
if anyone could mark this is a duplicate of bug 712898, it would be very much appreciated.
Comment 7•10 years ago
|
||
We'll still follow GTK in letting let Xft.dpi and corresponding Xsettings provide a logical dpi override for physical dpi, but bug 712898 will track implementing a solution here.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•