Bug 6126 - The control bar handle might be in the way
Summary: The control bar handle might be in the way
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.8.0
Assignee: Samuel Mannehed
Keywords: relnotes, thomas_tester, upstream
Depends on:
Blocks: 6132
  Show dependency treegraph
Reported: 2017-01-10 10:01 CET by Samuel Mannehed
Modified: 2017-03-27 14:19 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Samuel Mannehed cendio 2017-01-10 10:01:16 CET
Currently the control bar handle in the HTML5 client GUI can only be moved vertically along the height of the control bar. It is possible that it might be in the way for something in the session.

Upstream noVNC allows the control bar to moved to either side.
Comment 1 Samuel Mannehed cendio 2017-01-10 13:29:28 CET
(In reply to comment #0)
> Upstream noVNC allows the control bar to moved to either side.

See https://github.com/novnc/noVNC/pull/725

Another point worth noting is that currently in upstream, there is no way for a user to know that the control bar can be moved. There is a open PR for displaying a hint for this:

Comment 3 Samuel Mannehed cendio 2017-02-03 16:07:20 CET
This is fixed now.
Comment 4 Thomas Nilefalk cendio 2017-02-08 12:35:09 CET
Tested on MacOS Chrome and Safari and works, except for noted enhancements (visible clue) and/or documentation?

(For posterity: you can pull on any part of the control bar or the tab in extended or retracted state, but you get no visual feedback until you are actually on the other side of the screen. And you have to pull all the way to make it move.)

A suggestion for a visible clue would be a small dotted "touch area" on the upper end of the control bar, somewhat like the small pull-out tab. Maybe also restrict moving to just be allowed with this area. I'd also like an outline when I drag to give visual feedback that it is a supported action.

Note You need to log in before you can comment on or make changes to this bug.