[
https://issues.apache.org/jira/browse/GUACAMOLE-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888744#comment-17888744
]
Mike Jumper commented on GUACAMOLE-1953:
----------------------------------------
{quote}
Maybe the screen height needs to be updated when the Android keyboard opens?
{quote}
We actually already do exactly this. In cases where a mobile browser shoves the
display off the top of the screen when the native keyboard opens, this is
because the browser provides no indication whatsoever that this has happened.
The window size exposed to JavaScript is unchanged, the scroll position is
unchanged, and no events are fired. The browser simply moves the viewport
halfway off the screen without any way for JavaScript to see this.
We can double-check whether there's something missing, but it's possible that
there is simply nothing that can be done for this particular browser. If that's
the case, your only option would be to use the non-native on-screen keyboard,
and we should probably look into providing a mobile-friendly variant of
Guacamole's on-screen keyboard.
[~sagl]: What specific Chromium-based browser are you using?
> Issues with native on-screen keyboard (input line) and screen scrolling
> up/black gap
> ------------------------------------------------------------------------------------
>
> Key: GUACAMOLE-1953
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1953
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.5.5
> Reporter: Sandro
> Priority: Minor
> Attachments: Medien.jpg
>
>
> On phones with Chromium-based browsers, tapping the input line always moves
> the screen image to the top. The top half of the screen is no longer visible.
> Instead, there is a large black gap.
> It's not possible to move the screen up or down, and the input on the VNC
> screen is no longer visible, and you have to type blindly.
> I understand that this is because the position of the input line does not
> match the actual VNC input field, and Chrome tries to zoom in to where you
> are typing. However, the Firefox browser also seems to handle this much
> better. Maybe the screen height needs to be updated when the Android keyboard
> opens?
> Are there any workarounds or solutions to this problem?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
