* Hide lossless if not supported and tweak logo style
Co-authored-by: ryan.kuba <ryan.kuba@kasmweb.com>
Co-authored-by: mattmcclaskey <matt@kasmweb.com>
* KASM-4109 update to new logos and ensure lossless is only shown as an option on setups that support it
* KASM-4109 add css changes for loading screen
* change logo background color, removed lossless changes
---------
Co-authored-by: ryan.kuba <ryan.kuba@kasmweb.com>
Co-authored-by: mattmcclaskey <matt@kasmweb.com>
* KASM-3972 use an array of known scaling values to produce pixel perfect output
* KASM-3972 drop automatic pixel perfect support to only 1.25 and 1.5 ratios common to Windows installations
* KASM-3972 change setting name and commit html changes
---------
Co-authored-by: ryan.kuba <ryan.kuba@kasmweb.com>
* Major refactor of display.js queue to assume async rect processing in order to accommodate threaded decode or udp
* QOI lossless decoder on worker threads using WASM
* rfb.js class to provide frame_id and rect counts per frame
Co-authored-by: ryan.kuba <ryan.kuba@kasmweb.com>
Co-authored-by: matt <matt@kasmweb.com>
* KASM-2090 work around for incomplete webp images when there are lots of concurrent users on a single session. Unknown root cause, work around will in most cases keep the connection alive.
* KASM-2053 Fixes previous issues where there was no difference between medium and high
* Expands quality settings to adjust more rendering settings
* Adds an extreme quality setting and custom
* Adds the quality setting to the noVNC control panel, was previously only exposed in the backend for integration with Kasm Workspaces
* Switching quality settings no longer requires reconnecting.
Add several single and multitouch gestures to simulate various mouse
actions that would otherwise be impossible to perform.
This replaces the old system where you could select which mouse button
a single touch would generate.
This was done a bit arbitrarily before which could easily miss things,
end up in the wrong state and not trigger animations correctly.
This reverts commit c12e5b2b54 and fixes
things in a different way.
Very few browsers are left in the wild that supports modules but not
"nomodule", so let's simplify our handling a bit.
Safari 10 supports modules but not 'nomodule', this means that this
particular version of Safari will be broken. Due to this we have to
bump up the required Safari version to 11.
Chris Hunt
mattmcclaskey
Ryan Kuba
j-travis
Matt McClaskey
Mariusz Marciniak
Pierre Ossman
Samuel Mannehed
Chris Koying Browet
Juanjo Diaz