You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -213,6 +213,10 @@ If you plan on being notified everytime the form data are updated, you can pass
213
213
214
214
Sometimes you may want to trigger events or modify external state when a field has been touched, so you can pass an `onBlur` handler, which will receive the id of the input that was blurred and the field value.
215
215
216
+
#### Form field focus events
217
+
218
+
Sometimes you may want to trigger events or modify external state when a field has been focused, so you can pass an `onFocus` handler, which will receive the id of the input that is focused and the field value.
219
+
216
220
## Form customization
217
221
218
222
### The `uiSchema` object
@@ -954,6 +958,7 @@ The following props are passed to custom widget components:
954
958
-`readonly`: `true` if the widget is read-only;
955
959
-`onChange`: The value change event handler; call it with the new value everytime it changes;
956
960
-`onBlur`: The input blur event handler; call it with the the widget id and value;
961
+
-`onFocus`: The input focus event handler; call it with the the widget id and value;
957
962
-`options`: A map of options passed as a prop to the component (see [Custom widget options](#custom-widget-options)).
958
963
-`formContext`: The `formContext` object that you passed to Form.
0 commit comments