-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Dynamic blur values #712
Comments
Can you explain more what it is you are trying to achieve? |
@ckosloski originally, we had textareas that would cancel whenever you blurred but users would type long content in those textareas, click outside of the form, and lose all that they had typed in the input. However, they do like the convenience of being able to click outside of the form if they haven't typed anything instead of having to find and click the cancel button. |
Why not just set the blur to submit? |
@ckosloski To answer your second question in the original comment, we are looking to avoid a backend call unless the user has hit the save button. |
Why can't you check the existence of data before submitting to backend? |
We recently ran into a feature request where users would like editable inputs to cancel on blur if nothing has been entered but ignore if the input has text. We attempted to set the
blur
attribute to something dynamic but it looks like the form only checks for the blur value in the compile step here.Can anything be done to allow for a dynamic blur value? Or can we add a
cancelIfEmpty
option forblur
?The text was updated successfully, but these errors were encountered: