Jasper Schelfhout

This is my local bug fix. Would this be recommended or not? within percentileRose() replacing `lpolygon(subdata$x, subdata$y, col = "white", border = NA) ` by ``` if(length(percentile) > 1) lpolygon(subdata$x,...

What currently worked for me is keeping `rownames = TRUE`, but setting all names to an empty string and making the column as small as possible. Note that `rownames(data)

@stla That's indeed the better approach, thank you! FWIW, I now realized I was working on a package where this trick was used: https://stackoverflow.com/questions/60406027/how-to-disable-double-click-reactivity-for-specific-columns-in-r-datatable ``` CSS

@mikmart Thank you for pinpointing the exact problem. I'm less familiar with plain HTML code. Is there any way we could somehow enforce `DT` to use a version of DataTables...

@mikmart Seems like it was indeed still working in the previous version of `DT`. This can be used as a temporary solution: `remotes::install_version('DT', '0.30')` Reported the bug on their free...

Quick update: apparently it's already fixed in the upcoming version of DataTables: https://datatables.net/forums/discussion/78109/bug-is-it-possible-to-fix-incremental-cell-dragging-autofill-extension#latest So I guess this issue can be closed as soon as the needed releases have happened and...

@AhmedKhaled945 You can use `input$dt_rows_current[input$dt_rows_filled]` instead of `input$dt_rows_filled`.

I discussed with @nathaneastwood and the core issue seems to be at SQLite side, where it allows to define quite some nonsense types. Even have no type at all. ```...

@krlmlr that makes sense. Thanks for thinking along, I think we can close this issue.