From 0620cec2996165b0a187a6a87e99209fa8a29540 Mon Sep 17 00:00:00 2001
From: Scott Feeney <scott@oceanbase.org>
Date: Tue, 9 Jun 2015 11:13:28 -0400
Subject: [PATCH] Merge pull request #4003 from
 AnSavvides/on-change-vs-on-input

[#3964] Add note about React's onChange vs. DOM's oninput
---
 docs/docs/07-forms.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/docs/07-forms.md b/docs/docs/07-forms.md
index 475c9183e4..4bad8ea7c8 100644
--- a/docs/docs/07-forms.md
+++ b/docs/docs/07-forms.md
@@ -28,6 +28,10 @@ Form components allow listening for changes by setting a callback to the `onChan
 
 Like all DOM events, the `onChange` prop is supported on all native components and can be used to listen to bubbled change events.
 
+> Note:
+>
+> For `<input>` and `<textarea>`, `onChange` supersedes — and should generally be used instead of — the DOM's built-in [`oninput`](https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/oninput) event handler.
+
 
 ## Controlled Components