fullscreen does not cover statusbar in dwm window manager (linux)

RESOLVED INCOMPLETE

Status

()

Firefox
Untriaged
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: William Houser, Unassigned, NeedInfo)

Tracking

({regressionwindow-wanted})

46 Branch
x86_64
Linux
regressionwindow-wanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce:

install Arch Linux, install and use dwm window manager upgrade from version 45.* to 46.*...tried to use full screen


Actual results:

full screen scrolled everything up except for the dwm status bar


Expected results:

fullscreen should have covered the entire screen. this was not a problem until version 46, and up. When I roll-back to the latest version 45, it works right
(Reporter)

Updated

2 years ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
(Reporter)

Comment 1

2 years ago
I just tried it with the i3 window manager on ArchLinux. fullscreen works fine with it. Seems to be specific to dwm

Comment 2

2 years ago
FF46 supports Gtk3 now. What's your Gtk version?

Updated

2 years ago
Flags: needinfo?(wchouser3)
(Reporter)

Comment 3

2 years ago
(In reply to Loic from comment #2)
> FF46 supports Gtk3 now. What's your Gtk version?

Gtk2 is 2.24.30-2

Gtk3 is 3.20.6-1 

fullscreen works fine with i3 window manager, as well as LXDE. It only seems to be a problem with dwm.
(Reporter)

Comment 4

2 years ago
just upgraded to version 47, and still having the same problem

Comment 5

2 years ago
Hello William, can you please provide regression range

http://mozilla.github.io/mozregression/documentation/usage.html

Thanks!
Keywords: regressionwindow-wanted

Comment 6

2 years ago
Closing the bug as resolved:Incomplete due to no response for requested info. Feel free to reopen if you still encounter this issue and please provide regression range. This would help us to identify where this issue got introduced.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.