# Bug Report - Text Input on Cloned Row Updates Original Component

**URL:** <https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310>\
**Category:** Questions about Thunkable X\
**Tags:** components, bug, textinput\
**Created:** [November 10, 2019, 1:09pm UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310 "2019-11-10T13:09:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![itmanager](https://avatars.discourse-cdn.com/v4/letter/i/edb3f5/32.png) [@itmanager](https://community.thunkable.com/u/itmanager)\
**Post date:** [November 10, 2019, 1:09pm UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310/1 "2019-11-10T13:09:59Z")

</div>

Hej Thunk-meisters!

I think I found a bug when cloning a Row component containing Text Input.  
[https://x.thunkable.com/copy/2f9bcfa99ca06cd252299c2e1b561223](https://x.thunkable.com/copy/2f9bcfa99ca06cd252299c2e1b561223)

If you type into the upper (original) Text Input, only that component shows the change. However, if you type into the lower (cloned) Text Input, both Text Input components reflect the edit.

I hope this helps!

@domhnallohanlon @actech

---

<div class="post-metadata">

**Author:** ![actech](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@actech](https://community.thunkable.com/u/actech)\
**Post date:** [November 10, 2019, 1:37pm UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310/2 "2019-11-10T13:37:23Z")

</div>

Excellent work. I’ll add it to my a bug-tracker for check fixes this bug - [https://x.thunkable.com/projects/5dbd5243a77acad1b26f851f/project/properties/designer/](https://x.thunkable.com/projects/5dbd5243a77acad1b26f851f/project/properties/designer/)

This bug is related not only to Row and Text Input. This is a common bug with cloned components in the row or column!

I add an extended message about this bug to Git.

---

<div class="post-metadata">

**Author:** ![maxb](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maxb/32/35200_2.png) [@maxb](https://community.thunkable.com/u/maxb)\
**Post date:** [June 9, 2020, 11:14am UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310/3 "2020-06-09T11:14:26Z")

</div>

Good to know.

In case you haven’t figured a work around, you can clone invisible components and make them visible

---

<div class="post-metadata">

**Author:** ![grahamb3210n9](https://avatars.discourse-cdn.com/v4/letter/g/2acd7d/32.png) [@grahamb3210n9](https://community.thunkable.com/u/grahamb3210n9)\
**Post date:** [October 11, 2020, 8:12pm UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310/4 "2020-10-11T20:12:22Z")

</div>

This is still a bug and preventing any dynamic content that includes a textinput

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [November 8, 2024, 11:27am UTC](https://community.thunkable.com/t/bug-report-text-input-on-cloned-row-updates-original-component/312310/5 "2024-11-08T11:27:41Z")

</div>