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 731317 - Fullscreened windows headerbar
Fullscreened windows headerbar
Status: RESOLVED DUPLICATE of bug 654051
Product: gtk+
Classification: Platform
Component: Widget: Other
3.13.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-06-06 05:58 UTC by Robert Roth
Modified: 2014-06-12 05:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Roth 2014-06-06 05:58:24 UTC 
With the migration to headerbars, application toolbars are disappearing, thus in case of fullscreened GtkWindows have to implement a custom component displayed only in fullscreen mode. For consistency, I think this component (shown always, or shown when pressing the mouse cursor to the top of the screen) should be handled by GtkWindow, to reduce code duplication.
Currently because of this, applications have to reimplement this (event handling for showing and hiding this widget) and they do it differently:
* gedit when fullscreened, animates the toolbar appearing
* evince always shows the toolbar when fullscreened
* eog just displays the toolbar without any animation.
Comment 1 Matthias Clasen 2014-06-12 03:10:51 UTC 

*** This bug has been marked as a duplicate of bug 654051 ***
Comment 2 Robert Roth 2014-06-12 05:03:12 UTC 
@Matthias: I feel like the bug report you have marked this as a duplicate of is talking about being impossible to click toolbar buttons of a fullscreened window by clicking at the edge of the screen, while this ticket was reported to unify fullscreened toolbar behaviour (autohide, animations) for gtk+ apps.

Should I comment these enhancement requirements (which have almost nothing to do with clicking at the screen edge and Fitts' law) on the other bug, and leave this as a duplicate?