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

Allow disabling inputs and outputs #3610

Closed
epruesse opened this issue Apr 7, 2022 · 0 comments
Closed

Allow disabling inputs and outputs #3610

epruesse opened this issue Apr 7, 2022 · 0 comments

Comments

@epruesse
Copy link

epruesse commented Apr 7, 2022

There are situations in which disabling input/output widgets is the best way to keep the user informed about possible actions, effective/applicable settings and possible outputs. This includes "graying out" the widget and making it non-reactive to events such as clicks or drag-drop.

One could argue that the need for this indicates bad UI design. Often that may be true, but it's still easier and shiny apps typically don't justify a month's worth of UX work. Disabled state is a simple and easy to understand way to convey that an input or output is in principle present, but at the current time not possible or not applicable.

Implementing this in third party extensions such as shinyjs is limited and difficult. Firstly, TypeScript widgets such as fileInput require deep meddling to turn off e.g. drag and drop features when they are disabled. Secondly, it's essential to have a universal visual for the disabled state (not so easy with things that are gray to start with).

It would be great to have this as a core feature, accessible via standard interfaces. E.g. fileInput(..., disabled=TRUE) and updateSelectize(..., disabled=TRUE).

@epruesse epruesse closed this as completed Apr 7, 2022
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

No branches or pull requests

1 participant