-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fileInput bypass submitButton behavior #45
Comments
See this thread: button that's not a submitButton |
Yes, you are right Nevertheless, the bug of submitButton+uploadFile remains, so I don't close the issue |
+1 fileinput bypass submitbutton |
+1 for this. |
Any eta on this functionality being addressed? |
submitButton edge case bugs are generally unlikely to be fixed; we'd deprecate that feature if we thought we could get away with it, as its overall design is flawed, making it susceptible to lots of bad edge cases. The actionButton/eventReactive/observeEvent family of functions are far superior, though there is a bit more up-front learning to do. |
Trying to use in the same ui a submitButton and a fileInput, it seems that when a file selection is done, the submitButton is not taken into account, that is to say, the output are processed immediatly.
Even if it could be taken as a bug, I think it should be more convenient to have an explicit event handling method for the submitButtton.
Something like a boolean which says if the last event was the press on this button (false if it was any other widget which was updated) ... But I don't know if it is possible with the shiny events policy...
It should also allow to use several buttons on the same ui.
Best regards,
Yann
The text was updated successfully, but these errors were encountered: