Samuel Mannehed (ThinLinc team)
Samuel Mannehed (ThinLinc team)
> So I think that is good enough for us to move forward with dropping IE support. It will be a glorious day
I agree, this would be nice. This was not a conscious decision, this is how the onscreen keyboard works on Android. It's difficult to make things work differently if you...
Perhaps it's possible to find a nice way to pause the `resizeObserver` in `showVirtualKeyboard()` and then resume it in `hideVirtualKeyboard()`.
This patch seems to work quite OK, do you mind giving it a try? diff --git a/app/ui.js b/app/ui.js index 95f938d..a2ceed3 100644 --- a/app/ui.js +++ b/app/ui.js @@ -1410,6 +1410,8 @@ const...
Yep, nothing happens Edit: when using tests/input.html I get this whenever I press a dead key: raw key event keyup (key: 0, char: 0, which: 0)
This would mean an extension of the RFB protocol, it is not trivial work.
If you mean that touch events should be passed to the desktop or application in the remote session, then we do need an extension to the protocol. The protocol only...
I believe we're waiting for a bugfix in Chrome. In a browser that works correctly, this is an improvement.
Agreed, sounds good. I'll commit. > The Readme lists under features "Local or remote cursor". As far as I can tell this option was disabled and Remote cursors will be...
@CendioOssman asked me to hold off with committing, said he has an objection.