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 696914 - fullscreen (e.g., gnome-terminal) disables hot corner
fullscreen (e.g., gnome-terminal) disables hot corner
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: overview
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-03-30 15:59 UTC by Grant Farnsworth
Modified: 2013-08-27 23:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Grant Farnsworth 2013-03-30 15:59:46 UTC
Fullscreening an application disables the hot corner--from what I can tell this is true of all applications.  I imagine this was probably implemented on purpose: probably someone felt that disabling the hot corner might be nice when, for example, watching a movie in fullscreen.  I don't agree with this, but I can imagine it.

However, there are some applications for which it really doesn't make sense to disable the hot corner when fullscreened.  For example, I've been using gnome-terminal in fullscreen mode lately.  In all other ways it behaves nicely, but if I want to switch viewports or applications I have to use alternatives to the overview because the hot corner doesn't work.

In my opinion the best option is to keep the hotcorner enabled for all applications.  But if there's a legit reason for some applications to disable the hotcorner when fullscreened, at least make it possible for applications, like gnome-terminal to not have this trait.
Comment 1 Allan Day 2013-08-27 23:03:04 UTC
Hi Grant, thanks for the bug report.

I wouldn't want to fix this without addressing bug 695352 at the same time, so marking this as a duplicate. I'll bring up your issue there.

*** This bug has been marked as a duplicate of bug 695352 ***
Comment 2 Jasper St. Pierre (not reading bugmail) 2013-08-27 23:12:15 UTC
Well, this has actually been fixed when we ported to barriers. Those work in all applications.