Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Remotescripts] Prevent *new* clients from running already executing remotescripts #191

Closed
nothingface0 opened this issue Aug 1, 2022 · 0 comments
Labels
backend Back-end related issues frontend Front-end related issues

Comments

@nothingface0
Copy link
Contributor

Currently, when a remotescript starts executing, only clients which have already connected (i.e. users which have opened a remotescripts page) are updated with the fact that the script execution started.

When a new client connects (e.g. a new browser tab of the same script) and the script is already under execution, the client is able to press the Submit button.

There should be a common state stored somewhere for all WebSocket clients, so that any new client is updated with the current state upon page load.

@nothingface0 nothingface0 added frontend Front-end related issues backend Back-end related issues labels Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Back-end related issues frontend Front-end related issues
Projects
None yet
Development

No branches or pull requests

1 participant