Hotfix: browser RDP mouse offset / blur / performance / taskbar (display-scale + coord fix)

[CallMeTechie]

Hotfix: browser RDP mouse offset / blur / poor performance / cut-off taskbar

Several linked problems on a HiDPI (125%-scaling) display, all rooted in display-scale / coordinate handling in public/js/rdp-player.js:

• Mouse cursor offset from the host cursor (and "fanning out"/trailing): the mouse handler sent raw element-space coordinates; guacd expects remote-desktop pixels. Fixed by dividing by display.getScale() and sending a proper Guacamole.Mouse.State.
• Taskbar cut off / had to click "Fit" manually: the fit-scale was only wired to display.onresize. Now also applied in onstatechange CONNECTED → the display auto-fits the container on connect.
• Poor performance + soft image: the player rendered at physical pixels (container × devicePixelRatio) → 1.5–2× more pixels for guacd to encode/transfer, plus downscale-smoothing blur. Now sends the container's CSS pixel size + dpi=96 so the remote desktop matches the viewport (fit-scale ≈ 1) with far less data over the tunnel. Dynamic-resize sendSize also uses CSS px.

Verified live vs real guacd 1.6.0 at deviceScaleFactor 1.25:

• WS width/height = CSS viewport px (1280, not 1600), dpi=96.
• Auto-fit: scale 1.0, display fits the container (no manual Fit).
• Mouse: for a fixed 1920×1080 route at scale 0.62, a click at element+(200,100) sends remote (321,161) = coords ÷ scale (offset fixed).
• guacd connects, no dpi warning. node --check clean; player-logic 5/5.

RDP-live (sharpness/feel) = the maintainer's manual acceptance. Pure HiDPI crispness is a tradeoff vs performance; a fixed high resolution can be set per-route for sharper output.

🤖 Generated with Claude Code