- 25 Jun, 2015 5 commits
- 24 Jun, 2015 1 commit
-
-
samhed authored
* Fixes #502 so that the viewport drag functionality can't get stuck
-
- 16 Jun, 2015 1 commit
-
-
samhed authored
"jumping around". Enable/disable the button instead of show/hide on these devices.
-
- 12 Jun, 2015 2 commits
- 19 May, 2015 2 commits
-
-
samhed authored
* This fixes backspace when using the on-screen keyboard on Android
- 05 May, 2015 1 commit
-
-
Samuel authored
Removed old no longer existing vnc.js and added playback.js
-
- 04 May, 2015 2 commits
-
-
Samuel authored
Make noVNC compatible with Content Security Policies
-
Fabian Zaremba authored
-
- 29 Apr, 2015 1 commit
-
-
samhed authored
* Disable local cursor when the browser doesn't support data uri
-
- 07 Apr, 2015 1 commit
-
-
Solly authored
slip in PATH for 'npm test' as not everyone has karma
-
- 27 Mar, 2015 2 commits
- 26 Mar, 2015 3 commits
-
-
Solly Ross authored
Previously, if an error was thrown from the Display constructor in the RFB constructor, we would attempt to use `RFB#updateState` to handle this. However, `RFB#updateState` attempts to close the WebSocket connection, which doesn't exist at this point. In the constructor, it's probably just better to raise an exception instead (making sure to clean up anything relevant). Fixes #460
-
Solly Ross authored
In e543525f, we switched to creating a new RFB object on disconnect. This caused issues, however, since any errors were only displayed briefly before the new "loaded" text was displayed instead. Now, we create the RFB object on connect. This essentially removes the usefulness of the "loaded" state, but prevents the aforementioned problem. To facilitate this, the code which does detection of cursor URI support was moved from this Display constructor (which now calls the new function) into its own function, `Util.browserSupportsCursorURIs()`. Fixes #467
-
Solly Ross authored
Previously, in launch.sh, `$HERE` was the directory of `$0`. However, if `$0` was actually a symlink, `$HERE` would be wherever the symlink was, which could cause issues (for example, the script wouldn't be able to local `$WEB` or `$WEBSOCKIFY` properly). Now, `$HERE` looks at whatever `$0` points at instead. Closes #447.
-
- 11 Mar, 2015 1 commit
-
-
samhed authored
-
- 10 Mar, 2015 1 commit
-
-
Solly authored
Fix resize in Firefox on Android
-
- 09 Mar, 2015 1 commit
-
-
samhed authored
* Renamed and reworked fbuClip to clippingDisplay * Added tests for clippingDisplay * Use the a noVNC_container which covers the entire page to get the full size (Fixes #463) * Added maxWidth and maxHeight to the canvas which can limit the viewport size * Only show either the canvas or the logo, hide one when the other is shown * Always center the canvas (previously it was only centered when not clipping) * Removed iOS specific "position-fixed" fixes and start calling setBarPosition on every resize * Removed the noVNC_screen_pad
-
- 05 Mar, 2015 3 commits
-
-
samhed authored
* Added better error handling in ExtendedDesktopSize * Added helper function to share code with DesktopSize * Update test.rfb.js to only check for error handling if we were the ones requesting the resize
-
samhed authored
Make the touch-keyboard code more robust through verifying that global variables are set before use.
-
Samuel authored
Introduce Local Autoscaling
-
- 03 Mar, 2015 1 commit
-
-
Solly Ross authored
This commit adds two new addition scaling options. Both options do local scaling. The first "Local Scaling", does both upscaling and downscaling. The second option, "Local Downscaling", only downscales. This is based on work by @mightypenguin (with an additional bug reported by @glazik12).
-
- 27 Feb, 2015 6 commits
-
-
Solly Ross authored
This commit updates the UI to allow for different scaling modes. The "resize" option was changed to be a dropdown with the following options: "None" (nothing), "Remote Resizing" (SetDesktopSize).
-
Solly Ross authored
This commit makes Travis launch sauce connect, instead of using karma to start Sauce Connect
-
Solly authored
Make Util.getPosition be relative to page
-
Solly Ross authored
Commit 5108c463 caused a regression in the case where scrolling is used -- getPosition return position relative to the viewport, while getEventPosition expected a position relative to the page. As per https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect, the fix for this is simply to add the `pageXOffset` and `pageYOffset` to the output of `getBoundingClientRect()`. Fixes #459.
-
Solly Ross authored
This commit increases the browserNoActivityTimeout to 100s (from the default of 10s) in an attempt to alliviate the timeout issues that we are seeing.
-
Solly Ross authored
This commit updates the test dependencies to the latest versions.
-
- 26 Feb, 2015 1 commit
-
-
Samuel authored
Fix disconnect/reconnect issues
-
- 25 Feb, 2015 1 commit
-
-
Solly Ross authored
Commit 155d78b3 prevented reconnections from working properly. This fixes that by creating a new RFB object after disconnecting or failing. Furthermore, this ensures that a new connection cannot be opened util we've actually disconnected (either by timer or by receiving a `close` event). Closes #452
-
- 20 Feb, 2015 1 commit
-
-
Solly Ross authored
This commit removes the old debian packaging information, which is out of date. People who wish to create Debain packages for noVNC are better off using the package information from the actual Debian or Ubuntu packages. Closes #453
-
- 18 Feb, 2015 1 commit
-
-
Solly Ross authored
Issue #449 pointed out that there were some files that were missed in 6f514864. This fixes that. Closes #449 Closes #450
-
- 17 Feb, 2015 2 commits
-
-
Solly Ross authored
When `utils/launch.sh` clones websockify, it can be cloned into the incorrect directory, depending on how `utils/launch.sh` is run. This commit ensures that websockify is always cloned into `utils/websockify`.
-
Solly Ross authored
Somehow, `utils/websockify` itself manage to sneak back in to 6f514864. This actually removes it.
-