You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Save input text in Input field inside Dash Editable Datatable without pressing 'Enter' key? #948
Hi All,
On entering a value in an input field inside an editable datatable, the user must press 'Enter' key to save it. Instead, if the user simply clicks outside of this cell, the value provided is not saved and the previous state is visible.
Is there a way by which we can save the input provided when focus moves out without pressing 'enter'?
@AnSohal can you give an example of code showing this problem, and also state the version of dash you're using? If I try this on https://dash.plotly.com/datatable/editable it works, the new value is accepted when I click to a new cell.
Thanks @AnSohal - it was the double click I was missing, it works fine with a single click but I see the behavior you're referring to when I double-click. This is indeed a bug, we should be able to fix it.
Reacted by mak, C. Travis Johnson and Jeffrey Ruder
Activity
alexcjohnson commentedon May 25, 2022
@AnSohal can you give an example of code showing this problem, and also state the version of dash you're using? If I try this on https://dash.plotly.com/datatable/editable it works, the new value is accepted when I click to a new cell.
t-mtzw commentedon Jun 2, 2022
@alexcjohnson
I tried the suggested site(https://dash.plotly.com/datatable/editable) to see if this problem occurs.
The following steps caused this problem.
1.mp4
This problem did not occur until dash-table==4.9.0.
2.mp4
3.mp4
The code used is the same.
Libraries used.
dash-table==4.9.0
dash-table==4.10.0
alexcjohnson commentedon Jun 3, 2022
Thanks @AnSohal - it was the double click I was missing, it works fine with a single click but I see the behavior you're referring to when I double-click. This is indeed a bug, we should be able to fix it.