GNOME Bugzilla – Bug 665819
messaging tray hot corner woe
Last modified: 2012-10-25 21:14:45 UTC
I use a laptop. I have my windows maximized for efficiency, mainly, but not only the web browser. I have done that for a very long time, even on MacOS. Each time I try to scroll down in Firefox, for example, I end up not being able too because the message tray decide to show up when the pointer is enough in the corner. (I got told in #gnome-shell to say that to design. instead I file a bug here, you can track it). This is not a unique case, and the only workaround beyond revamping the feature that the message-tray provides is to make it visible all the time, of course adjusting the actual visible rect to match it for maximized Windows.
adding keyword following this: <hub> does design read bugzilla? or this also a black hole? <hadess> hub: we do, when there's the ui-review flag set
*** Bug 665319 has been marked as a duplicate of this bug. ***
From Bug 665319 comment 0: > This occurred to me when I was watching my friend using my computer (F16 + > GNOME 3.2). > > Situation: > * Firefox is opened in full-screen mode > > Action: Move mouse to the bottom right edge of the screen to press the little > arrow on the scroll down. > > Planned outcome: Pressing the left mouse button scrolls down > > Actual outcome: The message-tray (empty) pops up. She clicked numerous times > and nothing happens. She moves the mouse back and forth a few times. At some > point she happens to be as far away from the corner to be able to scroll. > > This was very interesting to see especially because the figured out how to > switch between windows and how to start apps pretty quickly. > > (This never happens to me because I almost always use the mousewheel to > scroll). > > Possible solution: > * Use the bottom right corner as hot corner > * Increase the speed / time needed to access the hot corner > * Leave a gap in the corner of the message tray where clicks are actual going > "through" the message tray
(In reply to comment #1) > adding keyword following this: > > <hub> does design read bugzilla? or this also a black hole? > <hadess> hub: we do, when there's the ui-review flag set And here I am. The current redesign for scrollbars [1] removes the stepper buttons, which will much reduce this problem. If the issue persists we could try an alternative way of activating the tray using the pointer. One idea is to raise the tray when the pointer is pushed against the bottom screen edge a few moments. [1] https://live.gnome.org/GnomeOS/Design/Whiteboards/Scrolling#Tentative_Design
This is kind of similar to the bug about the opposite corner; the hot corner for the Activities button: bug #663661. In there, I posted a patch to add a little timeout to the hot corner, so the Activities overview doesn't activate if I overshoot with the mouse while trying to hit a File menu. Maybe the hot corner for notifications needs a similar timeout...
Moving the message-tray to the bottom-left corner (not used for the moment) would also solve the issue.
(In reply to comment #6) > Moving the message-tray to the bottom-left corner (not used for the moment) > would also solve the issue. The problem would still appear at other times, even if they are less common cases. For example, Evolution's online/offline button is at the bottom-left corner.
(In reply to comment #4) > > The current redesign for scrollbars [1] removes the stepper buttons, which will > much reduce this problem. What will you do if the computer does not have a pointing device that support scrolling? (hint: check what MacOS 10.7 does in that case). I don't believe this is a good alternative (to say it will go away) Also I have had case where a stupid "layover" at the bottom of a webpage that had a dismiss button on the right and the tray appeared when trying to reach it... > If the issue persists we could try an alternative way of activating the tray > using the pointer. One idea is to raise the tray when the pointer is pushed > against the bottom screen edge a few moments. I have another idea: how about you get rid of it and find an alternative that works better. Some like what Android does could work. Like a notification icon at the top that when clicked show them.
(In reply to comment #8) > (In reply to comment #4) > > > > The current redesign for scrollbars [1] removes the stepper buttons, which will > > much reduce this problem. > > What will you do if the computer does not have a pointing device that support > scrolling? > (hint: check what MacOS 10.7 does in that case). > > I don't believe this is a good alternative (to say it will go away) I did write 'reduce'. > Also I have had case where a stupid "layover" at the bottom of a webpage that > had a dismiss button on the right and the tray appeared when trying to reach > it... > > > > If the issue persists we could try an alternative way of activating the tray > > using the pointer. One idea is to raise the tray when the pointer is pushed > > against the bottom screen edge a few moments. > > I have another idea: how about you get rid of it and find an alternative that > works better. Some like what Android does could work. Like a notification icon > at the top that when clicked show them. One of the main points of the design is not to have notifications displayed on screen the whole time. I'd like to explore other ways of improving the current design before we decide to throw the baby out with the bath water. Please, let's stick to the issue as reported.
(In reply to comment #9) > One of the main points of the design is not to have notifications displayed on > screen the whole time. I'd like to explore other ways of improving the current > design before we decide to throw the baby out with the bath water. > > Please, let's stick to the issue as reported. The issue as reported is that the message tray is always in the way, appearing when we don't expect it an so on. Yes it even break status icon that have menus (ie bad third parties) as it comes on top of the menu and block the bottom. The hot corner was one of the problem, but not the only - you changed the title to that. As for not having it displayed the whole time, there is another bug about missing IM notifications, for the exact same reason which show that the design goal to not have notifications displayed on screen the whole time isn't a good idea either. It wasn't two years ago, it still is not now.
(In reply to comment #10) > (In reply to comment #9) > > One of the main points of the design is not to have notifications displayed on > > screen the whole time. I'd like to explore other ways of improving the current > > design before we decide to throw the baby out with the bath water. > > > > Please, let's stick to the issue as reported. > > The issue as reported is that the message tray is always in the way, appearing > when we don't expect it an so on. It sounds like there are several issues here. If you are concerned about notifications appearing under the pointer, please see bug 661358 (now fixed). If there are other problems please file reports with specific examples. > Yes it even break status icon that have menus > (ie bad third parties) as it comes on top of the menu and block the bottom. > > The hot corner was one of the problem, but not the only - you changed the title > to that. I changed the title to reflect the issue that you described. > As for not having it displayed the whole time, there is another bug about > missing IM notifications, ... Yes, and it (bug 641723) is dependent on two other bugs that still need fixing (contributions welcome).
(In reply to comment #11) > > If there are other problems please file reports with specific examples. Fullscreen youtube videos are an example of controls being obscured by the tray. Another one is the "Today pane" switch in Thunderbird. In general, any application that puts controls by the bottom-right corner can be affected. The current design makes it difficult for developers to use that easily accessible corner in their applications. A related problem is that the on-screen keyboard appears from the bottom, like the messaging tray. To fix this problem, the keyboard now includes a dedicated "show tray" button: that this button exists is an indication that the whole solution might need another approach. I would rather that we included small notifications on the top bar and freed the rest of the screen for the apps' content.
The message tray design is being updated for 3.6, and hot corner issues are being looked at as a part of that: https://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/#A3.6_Refresh_Proposal
(In reply to comment #0) > Each time I try to scroll down in Firefox, for example, I end up not being able > too because the message tray decide to show up when the pointer is enough in > the corner. The hot corner is gone, the tray is never triggered while a mouse button is pressed, and it is never shown without explicit user action (which used to be the case after hiding the banner notification). There are plans for further improvements to how the tray is triggered (e.g. make it even less likely to be triggered accidentally), but those depend on pending Xorg changes (see bug 677215). Still, I consider the current iteration enough of a fix for the original issue to close the bug.