jlesage / docker-baseimage-gui

A minimal docker baseimage to ease creation of X graphical application containers
MIT License
1.2k stars 179 forks source link

Hide "noVNC_control_bar" when using the virtual keyboard? #94

Closed Febtw closed 1 year ago

Febtw commented 1 year ago

docker-baseimage-gui version: 4.3.6

When using the virtual keyboard, "noVNC_control_bar" blocks out some area of the page. But if I close the "noVNC_control_bar", the virtual keyboard is closed with it.

on my laptop Edge in emulate mode image

on ipad safari 1

I think the noVNC of recent version is able to use the virtual keyboard and have "noVNC_control_bar" hidden. The following noVNC is installed through ubuntu 20.04 repo last month, but I don't know how to find the version of it. 1

1



I have tried to update noVNC to 1.4.0 according the Dockerfile of "docker-baseimage-gui", but fail to use.

image Dockerfile.txt

jlesage commented 1 year ago

So if I understand correctly you request, you would like the virtual keyboard to remain active when closing the control menu. Do you see the same behaviour with version 4.2.2 of the baseimage?

jlesage commented 1 year ago

I was not aware of the new version of noVNC. I will have to integrate it.

Febtw commented 1 year ago

So if I understand correctly you request, you would like the virtual keyboard to remain active when closing the control menu. Do you see the same behaviour with version 4.2.2 of the baseimage?

Yes, I would like the virtual keyboard to remain active when closing the control menu. And yes, I see the same behaviour with version 4.2.2 of the baseimage.

Dockerfile with baseimage-gui 4.2.2.txt

The startapp.sh has only one command /usr/bin/freeplane %F .

jlesage commented 1 year ago

Ok, I did more investigation on that and from what I understand, you should get this behaviour with both noVNC 1.3.0 and 1.4.0. However, this behaviour can be easily adjusted, so the next version of the image will have the fix for that.

Febtw commented 1 year ago

Thanks a lot!

jlesage commented 1 year ago

This should be fixed with version 4.4.0.

Febtw commented 1 year ago

This should be fixed with version 4.4.0.

Yes, new version is good!