Pierre Ossman (ThinLinc team)

The relevant file is `core/input/mouse.js`. Any debugging you can do would be helpful.

I've debugged this, and it is unfortunately some bug in Chrome. I've reported it to them here: https://bugs.chromium.org/p/chromium/issues/detail?id=1098276 For now we'll wait and see how they respond.

Ehm... #364 is about a security type, not an encoding. Or am I missing something?

I'm not a huge fan of configuration to work around bugs, but let's see what this turns in to...

That's pretty much per design and happens on any hidpi device. The reason being that the other end usually assumes a "standard" PPI, so we scale things according to CSS...

I think noVNC should stick to VNC and avoid side channels. So the easiest first step would probably be too look at existing VNC extensions for audio. QEMU's variant is...

Either a draft PR, or share your repo on the devel mailing list and we can discuss things there.

I'm trying to test this but I'm getting very choppy audio. Any suggestions on debugging and getting it working?

Sorry about the delay. I could spend a little time on this today, but unfortunately not a lot. The proxy doesn't log anything so I'm afraid there is no help...

@lhchavez, were you able to get a docker image up for testing?