Skip to content

update - restore orig clipboard#28

Open
mloginov wants to merge 26 commits into
masterfrom
17701_update_orig_clipboard
Open

update - restore orig clipboard#28
mloginov wants to merge 26 commits into
masterfrom
17701_update_orig_clipboard

Conversation

@mloginov
Copy link
Copy Markdown
Member

Felso Daniel (McP/MFE4) and others added 26 commits October 8, 2025 13:04
The warning prompt is only displayed if there is an active connected
session, when viewOnly is disabled.
We are using OIDC now instead of the old style access tokens.
Apparently publishing with OIDC as an auth method only works with npm
11.5.1 and onward.
Node 24 comes with npm > 11.5.1 which we need in order to publish with
OIDC auth.

This also reverts the change in commit e03a54e, which broke the
publishing step.
This should have been a part of commit 243d7fd
This should have been a part of commit 243d7fd
Add a new configuration option `keep_device_awake` to allow noVNC to
stop the local display from going to sleep. This is especially useful
with view-only sessions.

This new option has been added to the configuration UI, making it easier
for users to configure. When this option is changed at runtime, we will
request/release the wake lock.

We only hold the view lock while connected to a server. We will also
attempt to reacquire the wakelock if we lost it due to a visibility
change (the tab becoming inactive, or during the transition into/from
fullscreen).

All existing unittests have been run, and the change has been manually
tested in Firefox 145. Additional tests will be added later.
Add an error state to the WakeLockManager state machine. This adds a
transition that can be detected from tests (it otherwise serves no
purpose, and the system immediatly transitions back into the released
state).
Dispatch an event on each state transition inside the WakeLockManager.
This gives the unit tests something to synchronise on, allowing us to
write fast, flake-free tests.
Add tests to for both the `rfb` side (calling into the new wakelock
code), and the new wakelock class (which tracks the desired state and
how to get there).
I noticed a simple typo - "inoder rendering"
We shouldn't be advertising these if we'd like people to stop using
them.
Mainly to keep eslint happy with its new recommended rules. But it also
makes the code more clear to not have unused stuff in it.

The des code got a bit more refactoring since eslint was upset about the
final "i++" as it was technically an unused assignment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants