window.screen.availWidth is much smaller than what it should be on my machine
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: bbouvier, Unassigned)
Details
I've got a large screen with a resolution of 1920x2650. I am using the i3 window manager (which might be the reason why I can see this bug).
If I run window.screen.availWidth on any tab of my browser, it returns 405, while window.screen.width is window.screen.width is 1621. When I start Firefox, I don't have any other app running on the same virtual screen (so, no split), thus Firefox should be able to use the full width.
Chromium does it correctly, and finds the correct values for both window.screen.width and window.screen.availWidth of 2560.
Relevant about:config prefs:
- layout.css.devPixelsPerPx: 1.3
- privacy.resistFingerprinting: false
This debug log: https://searchfox.org/mozilla-central/source/widget/gtk/ScreenHelperGTK.cpp#160
Prints the following:
[(null) 14669: Main Thread]: D/WidgetScreen New screen [1920 0 2560 1440 (1920 0 640 1440) 24 1.000000 1.000000 104.802284]
Because of this bug, Phabricator always thinks that I'm using a phone device; arguably there's a bug on their side too (they should have an event handler on resize, or not use window.screen.availWidth), but I thought it'd be interesting to report this here as well.
|
||
Comment 1•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 2•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 3•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 4•5 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal to S3.
Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.
|
||
Comment 5•2 years ago
|
||
Closing as it seems too niche and no activity for 3 years. Désolé Benjamin
Description
•