From c6955fed2672c1eaa8882417ea5bca65893f5b40 Mon Sep 17 00:00:00 2001 From: petehunt Date: Wed, 10 Jul 2013 17:14:29 -0700 Subject: [PATCH] link to blog --- docs/refactor/03-handling-user-input.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/refactor/03-handling-user-input.md b/docs/refactor/03-handling-user-input.md index b3dd65667..eec106aaf 100644 --- a/docs/refactor/03-handling-user-input.md +++ b/docs/refactor/03-handling-user-input.md @@ -40,7 +40,7 @@ Under the hood React does a few things to keep your code performant and easy to **Autobinding.** Every method is automatically bound to its component instance. React caches the bound method such that it's extremely CPU and memory efficient. It's also less typing! -**Event delegation.** React doesn't actually attach event handlers to the nodes themselves. When React starts up, it starts listening for all events at the top level using a single event listener. When a component is mounted or unmounted, the event handlers are simply added or removed from a fast internal event mapping. When the event occurs, React knows how to dispatch it using this mapping. When there are no event handlers left in the mapping, React's event handlers are simple no-ops +**Event delegation.** React doesn't actually attach event handlers to the nodes themselves. When React starts up, it starts listening for all events at the top level using a single event listener. When a component is mounted or unmounted, the event handlers are simply added or removed from a fast internal event mapping. When the event occurs, React knows how to dispatch it using this mapping. When there are no event handlers left in the mapping, React's event handlers are simple no-ops. To learn more about why this is fast, see [David Walsh's excellent blog post](http://davidwalsh.name/event-delegate). ## How state works