1440240 - [CSD] When started maximized, extra drag space on the left end of the tab strip is present

Status: VERIFIED DUPLICATE of bug 1437647

(Core :: Widget: Gtk, defect)

Description

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 ID:20180221220150

STR:
1. Start Nightly.
2. Enable CSD (hide window header in the customization mode).
3. Maximize Nightly window.
4. Quit Nightly.
5. Start Nightly.
6. See the top left corner of the maximized window - there is a extra drag space present in the size similar to a pinned tab.
7. If you minimize and maximize the window again, the extra drag space correctly disappears.

Comment 1

[Dão Gottwald [:dao]]

(In reply to Michal Stanke (Mozilla.cz) [:MikkCZ][:mstanke] (use needinfo) from comment #0)
> STR:
> 1. Start Nightly.
> 2. Enable CSD (hide window header in the customization mode).
> 3. Maximize Nightly window.
> 4. Quit Nightly.
> 5. Start Nightly.
> 6. See the top left corner of the maximized window - there is a extra drag
> space present in the size similar to a pinned tab.

The bug here is that the window isn't actually maximized at this point.

Comment 2

[Marco Castelluccio [:marco]]

(In reply to Dão Gottwald [::dao] from comment #1)
> The bug here is that the window isn't actually maximized at this point.

Same as bug 1437647 then?

Comment 3

[Dão Gottwald [:dao]]

(In reply to Marco Castelluccio [:marco] from comment #2)
> (In reply to Dão Gottwald [::dao] from comment #1)
> > The bug here is that the window isn't actually maximized at this point.
> 
> Same as bug 1437647 then?

I guess so, except that this bug is in the right component and bug 1437647 probably isn't, assuming this is a Linux-only issue...

Comment 4

[Marco Castelluccio [:marco]]

(In reply to Dão Gottwald [::dao] from comment #3)
> (In reply to Marco Castelluccio [:marco] from comment #2)
> > (In reply to Dão Gottwald [::dao] from comment #1)
> > > The bug here is that the window isn't actually maximized at this point.
> > 
> > Same as bug 1437647 then?
> 
> I guess so, except that this bug is in the right component and bug 1437647
> probably isn't, assuming this is a Linux-only issue...

It might be a Linux-only issue, but I can't be sure since I mainly use Linux.