Bug 1651715 - After start maximized window is not restored but leaves black area
Summary: After start maximized window is not restored but leaves black area
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-20 16:01 UTC by rugk
Modified: 2019-02-19 10:39 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-19 10:39:23 UTC
Type: Bug


Attachments (Terms of Use)
Firefox with black area in overview (94.78 KB, image/png)
2018-11-20 16:01 UTC, rugk
no flags Details

Description rugk 2018-11-20 16:01:48 UTC
Created attachment 1507427 [details]
Firefox with black area in overview

Description of problem: After starting Firefox the maximized window is not restored but leaves black area around it.


Version-Release number of selected component (if applicable): all newer versions, this is not a new issue; but possibly Wayland-only; also happened in F28 IIRC


How reproducible:


Steps to Reproduce:
0. Firefox must be closed from a maximized state.
1. (Preferably after a computer restart) start Firefox.

Actual results:
The window is shown completely functional and "properly" in the top left corner

Expected results:
Maximize.

Additional info:
You can work around it by just dragging the window from the top once (then it is really de-maximized and you have it in your hand) and snap it back to the top, which maximizes it properly.

In the attached screenshot you can see it like that. I have cropped the top to hide my bookmarks and things like that, but they are all shown as expected. The screenshot is also made from the GNOME applications overview, as you can see from the blue border around the window, which I am hovering over.
Thus you can see it is really Firefox that has this fault, and unless you change the window size/maximization state in any way, it also stays like this.

Comment 1 rugk 2018-11-20 16:04:58 UTC
How reproducible: Sometimes. Not always.

Comment 2 Martin Stransky 2019-02-19 10:39:23 UTC
It's already tracked at upstream - https://bugzilla.mozilla.org/show_bug.cgi?id=1489463


Note You need to log in before you can comment on or make changes to this bug.