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
First off - many thanks for this library. Amazing attention to detail.
In my use case, I have rows with longText columns, some of which can contain 1MB or more of text.
To enable editing I used the textarea editor but the UX is poor with a lot of text.
I'd like, for the textarea editor to
pop out the textarea (I manually does this by hooking into the cellEditing event and modifying CSS)
don't close the text area on blur (eg if I use Ctrl-F to search in the textarea it closes)
cancel and save buttons (since we're not auto-saving on blur)
I've used the cellEditing event with a timeout of 100ms (because the textarea is not initialized right when the event fires).
Then I use the cellEdited and cellEditCancelled events to revert the CSS changes.
The CSS I use make the textarea position:fixed to pop it out of the table, with a fixed height/width
Arguably you could use a similar approach for "input" editor - showing a longer field for example. Maybe it makes sense to implement the input editor as actual input rather than making the div editable?
The text was updated successfully, but these errors were encountered:
Hi Oli,
First off - many thanks for this library. Amazing attention to detail.
In my use case, I have rows with longText columns, some of which can contain 1MB or more of text.
To enable editing I used the textarea editor but the UX is poor with a lot of text.
I'd like, for the textarea editor to
I've used the cellEditing event with a timeout of 100ms (because the textarea is not initialized right when the event fires).
Then I use the cellEdited and cellEditCancelled events to revert the CSS changes.
The CSS I use make the textarea position:fixed to pop it out of the table, with a fixed height/width
Arguably you could use a similar approach for "input" editor - showing a longer field for example. Maybe it makes sense to implement the input editor as actual input rather than making the div editable?
The text was updated successfully, but these errors were encountered: