-
-
Notifications
You must be signed in to change notification settings - Fork 1
Readonly mode #4
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
Comments
Thank you for acknowledging my work of writing solid documentation! That is really nice to hear! 😊 This 'readonly' feature is on the to-do list, indeed. But at the moment I have to prioritize more urgent tasks. After developing the many core components of VSM, I'm now focusing for a while on demonstrating VSM's usefulness in many application areas. This will be essential to secure stable funding and to develop more nice-to-have features. |
Here is a quick fix, perhaps: you could add a listener to your vsm-box, and when it emits a |
For now I will be preventing the events of some parts with css |
Ha, that's a clever fix! : ) For the contextual menus maybe the same approach does it... Have you tried setting
|
Yes, that's my fallback solution :-) display:none for those options but I was hoping for a exclude list of the options. Fair enough. In the end I might go for As a mini-request, perhaps the vsm-box events should respond to preventDefault. This way developers could intercept all events and disable them one by one as needed. |
After going through the great documentation of this project I have been unable to find any reference to readonly mode.
Is there any way to make the vsm-boxes readonly?, preventing the user from making any change but still able to show the popup for detailed information about the terms?
Thank you very much in advance.
The text was updated successfully, but these errors were encountered: