Open Bug 1405282 Opened 7 years ago Updated 2 years ago

Setting for More Window Drag Space on Maximized windows

Categories

(Firefox :: Toolbars and Customization, defect, P5)

57 Branch
defect

Tracking

()

Tracking Status
firefox56 --- unaffected
firefox57 --- wontfix
firefox58 --- wontfix

People

(Reporter: emanuele.84, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [reserve-photon-visual])

Attachments

(1 file)

In reference to bug #1349552 ,the option to add extra space actually isn't applied on maximized windows. 

I think the experience is not optimal since the user probably expects that enabling that option every window will gain that extra space (useful for fast gestures to resize and organize windows on many desktops shells).
Blocks: 1349552
Whiteboard: [photon-visual][triage]
Dupe of bug 1404497?
Flags: needinfo?(jhofmann)
(In reply to :Gijs from comment #1)
> Dupe of bug 1404497?

Partially. That bug refers to the drag space on the left and on the right of tabs. Here I'd like to point the space added at the top of tabs.

However, all the considerations about the UX are the same
Priority: -- → P4
Whiteboard: [photon-visual][triage] → [reserve-photon-visual]
IF not a dupe of bug 1404497 then I would say wontfix/invalid. I don't see much reason to add a space above tabs in maximized mode. If someone wish to have it, there is still an option to enable Titlebar and this will serve a purpose of it completely.
(In reply to Eddward from comment #3)
> IF not a dupe of bug 1404497 then I would say wontfix/invalid. I don't see
> much reason to add a space above tabs in maximized mode. If someone wish to
> have it, there is still an option to enable Titlebar and this will serve a
> purpose of it completely.

The user experience is still not optimal, the checkbox in customize mode can be checked without an effect. We'll figure something out.
Flags: needinfo?(jhofmann)
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to Eddward from comment #3)
> IF not a dupe of bug 1404497 then I would say wontfix/invalid. I don't see
> much reason to add a space above tabs in maximized mode. If someone wish to
> have it, there is still an option to enable Titlebar and this will serve a
> purpose of it completely.

I don't think that enabling the titlebar could be a good replacement for it.

Above all: is there any good reason to disable a feature that is already implemented for non-maximized windows, and that break the user experience? (that space is used desktop-wise to perform some gestures on lot of desktop environments).
See Also: → 1406136
Flags: qe-verify+
Priority: P4 → P5
Comment on attachment 8925503 [details]
Bug 1405282 - Show extra drag space even in fullscreen and maximized mode.

Stephen, I believe, also looking at the issues in bug 1406136, that there might be advantages in always showing the extra drag space, even in fullscreen or maximized mode. We would completely avoid the UX problem from this bug and respect the user choice consistently, without making assumptions about why or why not the user might want that space in maximized mode. 

As another option we could also just do that on OSX, which would resolve bug 1406136 but not help with this bug.

If you don't think this is a good idea, I'd just say we disable the checkbox in maximized mode the way we do it when the menubar or the titlebar are shown.

What do you think?
Attachment #8925503 - Flags: ui-review?(shorlander)
Assignee: nobody → jhofmann
Status: NEW → ASSIGNED
Priority: P5 → P1
Blocks: 1406136
See Also: 1406136
Is it still realistic that this'll make 58, or should we mark 58 as wontfix and try to get this in for 59 only at this point?
Flags: needinfo?(jhofmann)
I don't know. If Stephen is going to take a look we could land this quite quickly, though I don't think it's urgent to get into 58 either.
Flags: needinfo?(jhofmann) → needinfo?(shorlander)
Unassigning myself while we wait for an answer...
Assignee: jhofmann → nobody
Status: ASSIGNED → NEW
Downprio'ing to get this off radars given that there's no clarity about whether we want to ship this.
Priority: P1 → P3
Priority: P3 → P5
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:Gijs, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gijskruitbosch+bugs)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(gijskruitbosch+bugs)

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(stephen)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: