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
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -1432,6 +1432,7 @@ Of course, if you're making any sort of significant form, [you should use Formik
1432
1432
| FormEvent | Event that occurs whenever a form or form element gets/loses focus, a form element value is changed or the form is submitted. |
1433
1433
| InvalidEvent | Fired when validity restrictions of an input fails (e.g `<input type="number" max="10">` and someone would insert number 20). |
1434
1434
| KeyboardEvent | User interaction with the keyboard. Each event describes a single key interaction. |
1435
+
| InputEvent | Event that occurs before the value of `<input>`, `<select>` and `<textarea>` changes. |
1435
1436
| MouseEvent | Events that occur due to the user interacting with a pointing device (e.g. mouse) |
1436
1437
| PointerEvent | Events that occur due to user interaction with a variety pointing of devices such as mouse, pen/stylus, a touchscreen and which also supports multi-touch. Unless you develop for older browsers (IE10 or Safari 12), pointer events are recommended. Extends UIEvent. |
1437
1438
| TouchEvent | Events that occur due to the user interacting with a touch device. Extends UIEvent. |
@@ -1440,19 +1441,6 @@ Of course, if you're making any sort of significant form, [you should use Formik
1440
1441
| WheelEvent | Scrolling on a mouse wheel or similar input device. (Note: `wheel` event should not be confused with the `scroll` event) |
1441
1442
| SyntheticEvent | The base event for all above events. Should be used when unsure about event type |
1442
1443
1443
-
<details>
1444
-
<summary><b>What about <code>InputEvent</code>?</b></summary>
1445
-
1446
-
You've probably noticed that there is no `InputEvent`. This is because it is not supported by Typescript as the event itself has no fully browser support and may behave differently in different browsers. You can use `KeyboardEvent` instead.
Copy file name to clipboardExpand all lines: docs/basic/getting-started/forms-and-events.md
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -112,23 +112,11 @@ Of course, if you're making any sort of significant form, [you should use Formik
112
112
| FormEvent | Event that occurs whenever a form or form element gets/loses focus, a form element value is changed or the form is submitted. |
113
113
| InvalidEvent | Fired when validity restrictions of an input fails (e.g `<input type="number" max="10">` and someone would insert number 20). |
114
114
| KeyboardEvent | User interaction with the keyboard. Each event describes a single key interaction. |
115
+
| InputEvent | Event that occurs before the value of `<input>`, `<select>` and `<textarea>` changes. |
115
116
| MouseEvent | Events that occur due to the user interacting with a pointing device (e.g. mouse) |
116
117
| PointerEvent | Events that occur due to user interaction with a variety pointing of devices such as mouse, pen/stylus, a touchscreen and which also supports multi-touch. Unless you develop for older browsers (IE10 or Safari 12), pointer events are recommended. Extends UIEvent. |
117
118
| TouchEvent | Events that occur due to the user interacting with a touch device. Extends UIEvent. |
| UIEvent | Base Event for Mouse, Touch and Pointer events. |
120
121
| WheelEvent | Scrolling on a mouse wheel or similar input device. (Note: `wheel` event should not be confused with the `scroll` event) |
121
122
| SyntheticEvent | The base event for all above events. Should be used when unsure about event type |
122
-
123
-
<details>
124
-
<summary><b>What about <code>InputEvent</code>?</b></summary>
125
-
126
-
You've probably noticed that there is no `InputEvent`. This is because it is not supported by Typescript as the event itself has no fully browser support and may behave differently in different browsers. You can use `KeyboardEvent` instead.
0 commit comments