Closed Bug 1443571 Opened 6 years ago Closed 6 years ago

bad UI size: much too large

Categories

(Firefox :: Untriaged, defect)

60 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: vincent-moz, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180306100123

Steps to reproduce:

Start Firefox Nightly with a new profile.


Actual results:

The default UI (e.g. icons) is much too large, as if it were selected for a HiDPI screen. But the text in menus and tabs has the correct size. See attached screenshot of a part of the browser window.


Expected results:

The UI should have a normal size.

xdpyinfo output about my screen, in case this matters:

screen #0:
  dimensions:    2560x1440 pixels (602x342 millimeters)
  resolution:    108x107 dots per inch
I would add that at start up, the browser window didn't even fit on screen.
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180309100425

I cannot reproduce the issue on Ubuntu 16.04 x64 using Nightly 60.0a1(2018-03-06) and latest Nightly 60.0a1(2018-03-09).
I have an HiDPI screen: dimensions: 2560x1440 pixels (602x342 millimetres)
                        resolution: 108x108 dots per inch
I also found this: https://github.com/glium/glium/issues/1657. 

Not sure if this is a Firefox bug.
(In reply to roxana.leitan@softvision.ro from comment #2)
> I have an HiDPI screen: dimensions: 2560x1440 pixels (602x342 millimetres)
>                         resolution: 108x108 dots per inch

So, these are the same parameters as mine, and 108 DPI is not HiDPI.

> Not sure if this is a Firefox bug.

Hmm... The cause might be due to my buggy config to support HiDPI. FYI, I currently have in the firefox directory (corresponding to Nightly):

// IMPORTANT: Start your code on the 2nd line
var hdef = getenv("X11_HDEF");
if (hdef >= 2400) {
  pref("layout.css.devPixelsPerPx", "1.77");
} else {
  pref("layout.css.devPixelsPerPx", "-1.0");
}

(note: this test is buggy as this is not a HiDPI screen despite hdef >= 2400) and defaults/pref/default-prefs.js contains:

// https://developer.mozilla.org/en-US/docs/Archive/Mozilla/Automatic_Mozilla_Configurator/Locked_config_settings
// https://mike.kaply.com/2012/03/15/customizing-firefox-default-preference-files/
// https://mike.kaply.com/2012/03/16/customizing-firefox-autoconfig-files/
pref("general.config.obscure_value", 0);
pref("general.config.filename", "firefox.cfg");

But this is a configuration I've always had on this machine (with the same screen), i.e. since October 2015, and I've never seen any problem with Nightly before. I'll have to do some more tests next week.
Hi Vincent,

Could you please confirm that the problem wasn't reproducible on Nightly 59?
And if it is not, could you please assist further by doing a mozregression using your config? - hopefully, this will point us to the bug that introduced this issue.
Here is the mozregression link: http://mozilla.github.io/mozregression/documentation/usage.html and you will probably want to use mozregression --good 59 --bad 60

Thanks
Flags: needinfo?(vincent-moz)
I could test with a corrected config on the machine where I had the problem, and this is now OK.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(vincent-moz)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: