ced-b 6beda6a7ba Use calculated index instead of DOM index ... There seems to be a scenario when there are multiple `thead` entries in a table where some versions of Firefox (around 47) return -1 for `cell.parentNode.rowIndex`, which winds up with the whole top part being laid out wrongly. However, I looked this over and did not see any reason why not to use the calculated `i` for the row index instead.		2017-07-02 16:14:29 -05:00
..
extras	version bump	2015-10-31 11:06:09 -05:00
parsers	v2.28.11	2017-05-24 18:53:44 -05:00
widgets	Filter: Fix namespacing of events	2017-07-02 16:07:24 -05:00
jquery.tablesorter.combined.js	v2.28.14	2017-06-08 19:26:53 -05:00
jquery.tablesorter.js	Use calculated index instead of DOM index	2017-07-02 16:14:29 -05:00
jquery.tablesorter.widgets.js	v2.28.14	2017-06-08 19:26:53 -05:00