Answers

• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  February 1

  I've never tried to combine a Responsive child row renderer and a custom renderer as well - it should be possible, but I can well imagine that it wouldn't be easy.

  Responsive would ideally have row-level enable / disable via API, or at least ability to cancel render in responsive.details.renderer

  I never thought of adding that since you can just replace the renderer with what you want.

  The sounds like there is need for a renderer that would interface the two. I do like that idea, but I'll be honest, I don't know when I'll get time to try implementing that.

  Allan
• kthorngren Posts: 20,425Questions: 26Answers: 4,794

  February 1 edited February 1

  One option might be to disable the Responsive chid rows, like this example then use the Child Details solution to display the standard details plus the columns hidden via Responsive. I built this example to demo:
  https://live.datatables.net/qucicico/1/edit

  It uses the td.dt-control event from the Child Details. The format function is updated to get the responsive hidden columns using columns().responsiveHidden() and toArray() to turn it into a JS array for forEach(). For demo purposes it uses column().header() and column().dataSrc() to get the particulars about each hidden column. These are added to the child row display if hidden.

  It uses the responsive-resize and draw events to keep the child rows displayed on the page updated using the updateChildren() function via rows().every() with a selector-modifier of {page: "current"}. It uses row().child.isShown() to check the child row status and if shown updates the displayed HTML.

  Kevin