After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 738487 - Right or left docked windows are borderless making it difficult to distinguish from background windows
Right or left docked windows are borderless making it difficult to distinguis...
Status: RESOLVED DUPLICATE of bug 708857
Product: gtk+
Classification: Platform
Component: .General
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-10-13 21:44 UTC by Atri
Modified: 2014-10-14 13:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot showing docked nautilus on the left over a maximised nautilus in the background (59.99 KB, image/png)
2014-10-13 21:44 UTC, Atri
Details

Description Atri 2014-10-13 21:44:05 UTC
Created attachment 288425 [details]
Screenshot showing docked nautilus on the left over a maximised nautilus in the background

Windows docked to the left or right lose their window borders and this makes it impossible to tell them apart from windows that may be maximised in the background. If anything, it seems to me, borders for docked windows are all the more important that other "floating" windows to give the user some feedback on where the window's extent ends, e.g. while writing something in a gedit window docked to the left.

A screenshot probably explains better: the attached one shows a docked nautilus on the left over a maximised nautilus (inside a blank folder) behind it. No telling where the docked nautilus ends and where the maximised nautilus in the background begins in terms of screen estate.
Comment 1 Florian Müllner 2014-10-13 21:46:22 UTC
Those are client-side decorations, reassigning to GTK+.
Comment 2 Matthias Clasen 2014-10-14 13:36:13 UTC

*** This bug has been marked as a duplicate of bug 708857 ***