---
title: "Comment by Dinys Monvoisin on \"Why React Keys Matter: An Introduction\" | Hashnode"
description: "Interesting. I did not know about that. I never came across that. So from what I understand, react does not re-render the input field when using index. That&#39"
url: "https://hashnode.com/posts/why-react-keys-matter-an-introduction/5f603c311d6093023c713314/comment/5f608abc64c1f006b49e00c4"
---

[Discussion](https://hashnode.com/posts/why-react-keys-matter-an-introduction/5f603c311d6093023c713314)

Comment [Why React Keys Matter: An Introduction](https://hashnode.com/posts/why-react-keys-matter-an-introduction/5f603c311d6093023c713314)

[Dinys Monvoisin](https://hashnode.com/@dinmon)

[Sep 15, 2020](https://hashnode.com/posts/why-react-keys-matter-an-introduction/5f603c311d6093023c713314/comment/5f608abc64c1f006b49e00c4)

Interesting. I did not know about that. I never came across that.

So from what I understand, react does not re-render the input field when using index. That's why there is this issue. Am I right?

[Victoria Lo](https://hashnode.com/@victoria)

[Sep 15, 2020](https://hashnode.com/posts/why-react-keys-matter-an-introduction/5f603c311d6093023c713314/comment/5f608abc64c1f006b49e00c4#reply-5f60d4197317080b4cf5c427)

In React, components will automatically re-render if there are state changes. In this case, the input field does not re-render because there is no change in its value.

And because its key is mapped to the index instead of id, the position of the input field does not change with its corresponding list item.
