From 6f62758763a859518f5af067ef28e67a751278ea Mon Sep 17 00:00:00 2001 From: Ravishankar Rajagopalan Date: Sat, 25 Jun 2022 18:03:10 +0530 Subject: [PATCH] Change in Handling events page https://reactjs.org/docs/handling-events.html Handling Events -> Passing Arguments to Event Handlers Since the event argument may not always be second, but actually is always the last, this change proposes to make it clear. --- content/docs/handling-events.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/handling-events.md b/content/docs/handling-events.md index 6f2e6ed6d2e..f1ab3dc843b 100644 --- a/content/docs/handling-events.md +++ b/content/docs/handling-events.md @@ -145,4 +145,4 @@ Inside a loop, it is common to want to pass an extra parameter to an event handl The above two lines are equivalent, and use [arrow functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions) and [`Function.prototype.bind`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_objects/Function/bind) respectively. -In both cases, the `e` argument representing the React event will be passed as a second argument after the ID. With an arrow function, we have to pass it explicitly, but with `bind` any further arguments are automatically forwarded. +In both cases, the `e` argument representing the React event will be passed as the last argument after the ID. With an arrow function, we have to pass it explicitly, but with `bind` any further arguments are automatically forwarded.