migration from 1.10.16 to 1.10.18 breaking change for row()?

migration from 1.10.16 to 1.10.18 breaking change for row()?

MrSethTMrSethT Posts: 3Questions: 2Answers: 0

https://debug.datatables.net/itecuh

I upgraded today from 1.10.16 to 1.10.18 and where this line used to work...

var rowData = $('[id$="templateTable"]').DataTable().row(td).data();
is now required to be either
var rowData = $('[id$="templateTable"]').DataTable().row($(td).parent()).data();
or
var rowData = $('[id$="templateTable"]').DataTable().row(td.parentNode).data();
to work.

(the td variable is a valid td dom element from a table)

I see in the change log where some changes were made to the row selector in 1.10.17, but nothing mentions this change. Does .row() still take a table cell element as a row-selector?

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 61,726Questions: 1Answers: 10,109 Site admin
    Answer ✓

    Yes, I'm afraid this was an inadvertent bug that was introduced. It was reported here and fixed here. The nightly carries the fix until we do a 1.10.20 release.

    Allan

This discussion has been closed.