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 706129 - Fullscreen VM OSD extending to full width covers common active areas in guests
Fullscreen VM OSD extending to full width covers common active areas in guests
Status: RESOLVED DUPLICATE of bug 674664
Product: gnome-boxes
Classification: Applications
Component: display
3.8.x
Other Linux
: Normal normal
: 3.22
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
ui-design
: 707802 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-08-16 12:48 UTC by Stephen
Modified: 2016-03-31 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephen 2013-08-16 12:48:33 UTC
Maximised guest window controls, title bars etc. are covered by the OSD when mousing to anywhere at top edge and corners, making it very difficult to use them.

The current setup forces either a very slow mouse movement to avoid hitting the top edge when trying to use guest window controls, or if it's accidentally hit, a subsquent downward movement to escape the OSD, then a very cautious upwards movement to avoid re-showing it.

This effectively turns guest controls that have a very large Fitt's area into tiny targets.

For an example of a more unobtrusive implementation, see Vinagre's fullscreen OSD (a narrow centred collection of controls at the top edge of the screen). These could potentially be shown when mousing anywhere at the top edge and not just where they appear, as they wouldn't obstruct controls when the mouse cursor is elsewhere at the top edge.
Comment 1 Zeeshan Ali 2013-09-09 20:36:41 UTC
*** Bug 707802 has been marked as a duplicate of this bug. ***
Comment 2 Jakub Steiner 2013-09-09 22:54:06 UTC
I don't think the automatic fullscreening has proven itself and indeed the overlay toolbar for Boxes is prone to many unintentional OSD triggers.

We should be doing explicit fullscreening. The suggested solution for overlay controls is one approach to investigate. In addition we could rely on shortcuts and bringing up a banner when entering fullscreen ala web browsers (except using something like super+esc).
Comment 3 Zeeshan Ali 2013-09-09 23:10:06 UTC
(In reply to comment #2)
> I don't think the automatic fullscreening has proven itself and indeed the
> overlay toolbar for Boxes is prone to many unintentional OSD triggers.
> 
> We should be doing explicit fullscreening.

I don't understand. What has implicit fullscreening to do with this? Perhaps I'm misunderstanding what you mean by that?

> The suggested solution for overlay
> controls is one approach to investigate.

I think so too. I can give it a try after 3.10. As usual mockup will help. :P

> In addition we could rely on shortcuts
> and bringing up a banner when entering fullscreen ala web browsers (except
> using something like super+esc).

Yeah.
Comment 4 Jakub Steiner 2013-09-10 00:22:16 UTC
(In reply to comment #3)

> I don't understand. What has implicit fullscreening to do with this? Perhaps
> I'm misunderstanding what you mean by that?

Right now Documents and I believe Boxes too will go fullscreen when you view document/launch a box form a maximized window. 

> I think so too. I can give it a try after 3.10. As usual mockup will help. :P

Yea :)
Comment 5 Zeeshan Ali 2013-09-10 00:27:12 UTC
(In reply to comment #4)
> (In reply to comment #3)
> 
> > I don't understand. What has implicit fullscreening to do with this? Perhaps
> > I'm misunderstanding what you mean by that?
> 
> Right now Documents and I believe Boxes too will go fullscreen when you view
> document/launch a box form a maximized window. 

Then I assumed the correct meaning. This bug is about overlay toolbar obstructing guest control on the top in fullscreen mode so I don't think explicit fullscreening would help much, if at all.

BTW, we do show the overlay for a few seconds so that user knows there is a way out when entering fullscreen mode.
Comment 6 Jakub Steiner 2013-09-10 00:29:21 UTC
(In reply to comment #5)
> Then I assumed the correct meaning. This bug is about overlay toolbar
> obstructing guest control on the top in fullscreen mode so I don't think
> explicit fullscreening would help much, if at all.

What I meant is that fullscreening all the time makes the issue more relevant that it would be if you had to explicitly enter fullscreen and got the help/info banner.
Comment 7 Zeeshan Ali 2014-02-23 21:23:33 UTC

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