-
Notifications
You must be signed in to change notification settings - Fork 31
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
Role Vertification of LiveCanvas not working #676
Labels
Comments
httom111
added
bug
Something isn't working
new submission
Issues that have been filed and not yet processed by DRI
labels
Jul 27, 2023
I was able to replicate this, looking into it |
fix will be deployed in the next release |
Thank you for your response. Could you please inform me about the expected release date? I am working on a student project and need to plan around the release schedule. |
A new release is going out today @httom111 |
@httom111 v1.0.2 is now published, give it a try and let us know if you run into any issues. Thanks for your patience. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Please review FAQ and Known issues before filing a new item!
Please note: any submissions with insufficient reproducible information will be marked as 'Waiting for customer input' and may be closed is there is no response
Describe the bug
I am experiencing an issue with the "allowRoles" feature provided by the LiveCanvas library. Specifically, when I set up the system to allow only presenters to modify the canvas, meaning that they can trigger "wet stroke" events. If I understood correctly, only presenters should be able to draw on the canvas, while others should only be able to view it without making modifications. However, in my implementation, attendees are still able to modify the canvas.
To Reproduce
Set up the LiveCanvas with only the presenter role allowed to modify the canvas
Attendee attempts to modify the canvas
Expected behavior
Screenshots
Desktop(s) (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: