Bug 783557 - 3.26 redesign: left window buttons aren't on the left
3.26 redesign: left window buttons aren't on the left
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: shell
git master
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
:
: 787451 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2017-06-08 17:10 UTC by Jeremy Bicha
Modified: 2017-09-18 12:28 UTC (History)
3 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnome-control-center-alt-ambiance-left.png (39.91 KB, image/png)
2017-06-08 17:10 UTC, Jeremy Bicha
Details

Description Jeremy Bicha 2017-06-08 17:10:44 UTC
Created attachment 353411 [details]
gnome-control-center-alt-ambiance-left.png

gnome-control-center-alt built from git master on Ubuntu GNOME 17.04.

It sounds like there is a good chance that Ubuntu will keep its close,maximize,minimize buttons on the left. This does not work well with the redesigned gnome-control-center as these buttons are not on the far left, but to the right of the Search and app title area.

On the other hand, if the buttons are on the left then it gets crowded in that left sidebar and the app increases the sidebar width to compensate.

(Also, there could be a 4th window button there if a user has disabled GNOME's "Application Menu" in Tweak Tool.)

One easy way to test adding these extra buttons and putting them on the left is to use Tweak Tool 3.25.2+. The switches are near the bottom of the Windows page there.
Comment 1 Felipe Borges 2017-09-09 07:10:08 UTC
*** Bug 787451 has been marked as a duplicate of this bug. ***
Comment 2 Felipe Borges 2017-09-09 07:13:25 UTC
The patches (awaiting for review) in Bug 786692 seem to fix the issue for me. Could you please verify?
Comment 3 Jeremy Bicha 2017-09-18 12:28:30 UTC
(In reply to Felipe Borges from comment #2)
> The patches (awaiting for review) in Bug 786692 seem to fix the issue for
> me. Could you please verify?

Yes, this issue is fixed in 3.26.0. Thanks!

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