Answers

• allan Posts: 63,534Questions: 1Answers: 10,475 Site admin

  January 25

  I don't think there is a workaround for this I'm sorry to say. The problem is that Select is used the nodes to select rows with a shift click (a range). I'll need to change how it works a bit in order to solve this.

  Allan
• Diego123a73 Posts: 4Questions: 2Answers: 0

  January 25

  I guess for now I'll have to leave deferRender disabled and hope there's a solution some day

  Thank you Allan for such a quick response!
• allan Posts: 63,534Questions: 1Answers: 10,475 Site admin

  January 25

  I'll have a look for the upcoming release - it would be nice to get this in and fixed.

  Allan
• allan Posts: 63,534Questions: 1Answers: 10,475 Site admin

  January 26 Answer ✓

  I've just been looking at the code, and I was surprised that it wasn't working, so I've created a test case, and it does actually appear to be working for me. With the current releases: https://live.datatables.net/nafidaba/1/edit .

  To test, click a row in the table as it is loaded, then use the scrollbar to zip down the table. Shift click to select another row - there will be a large gap in the middle where rows weren't drawn, so they don't have any nodes displayed, but the rows will still be selected. Depending on how many rows you select, it might take a few seconds for the selection process to complete.

  Then to check that it works as expected on the console for that iframe run:

  $('#example').DataTable().rows().nodes().count()
  $('#example').DataTable().rows({selected:true}).count()
  

  For the selection and draws I've just done I get:

  234
  46087
  

  So 234 tr nodes drawn (at the start of the table and where I dropped the scroll), but 46k rows selected. Rows in the gap were selected and if I jump back up with the scroll bar I can see the rows are selected as they get rendered.

  Once thing I notice is that you are using:

  table.cells( { selected: true } ).data();
  

  Cell selection is different from row selection. Just because a row is selected, its cells are not. I'm not sure if you are selecting rows or cells in the UI? The two are orthogonal.

  Can you give me a link to a page showing the issue so I can look into it? The example I have above appears to be working as expected.

  Allan
• Diego123a73 Posts: 4Questions: 2Answers: 0

  January 29

  Hey allan, apparently I overlooked it and I was using

  table.cells( '.selected' ) 
  

  to get the cells instead of

  table.cells( { selected: true } )
  

  So the program was trying to read the selected cells from the HTML instead of the Select API, which is what clashed with the deferRender.
  Now that I switched it everything seems to be working as expected!
  Sorry for the troubles and thanks for looking into it
• allan Posts: 63,534Questions: 1Answers: 10,475 Site admin

  January 29

  Ah! That would do it. Thanks for letting me know

  Allan