69c750dd7205cc9ce4024aaf9a7104c9ca3abc2e
Both were enabled. They are alternative strategies, not complementary ones: resizeSession asks the server to become the container's size, scaleViewport scales whatever the server sends to fit. Running both means noVNC resizes AND then applies a scale factor, and any gap between the size requested and the size actually granted leaves a fractional scale that every pointer coordinate is mapped through. The visible symptom was a cursor offset from the real pointer, with clicks landing somewhere else. It only started mattering with the move to Xvnc. x11vnc could not resize, so resizeSession was inert and scaleViewport did all the work; Xvnc implements RandR SetDesktopSize, so now both are live and they interfere. Scaling is redundant now the session genuinely becomes the container size: pixels are 1:1 and there is no coordinate arithmetic left to get wrong. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%