You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have child rows marked with expand-child, tablesorter doesn't keep them together with the parent, so if you have a second match it replaces the child of the first row. For example:
first column, first row
second column first row
first child row
first column, second row
second column, second row
second child row
with this you can see that if you filter it you'll see the second row in place of the first child.
The text was updated successfully, but these errors were encountered:
Hmmm, this may be a bit more difficult to fix since in the child row demo, the table cells span across several cells, so the script ignores them. I guess I could make it completely ignore the child rows for now. Hmm, I don't like that idea either. Give me some time to think about it.
Ok, I think I figured it out... basically I made an option called widgetFilterChildRows.
When it's true, ALL child row content is included when checking the filter - this is because the child row spans across multiple columns. When false, the child row content is completely ignored.
I made a new demo that allows you to toggle this option to see the difference.
When you have child rows marked with expand-child, tablesorter doesn't keep them together with the parent, so if you have a second match it replaces the child of the first row. For example:
with this you can see that if you filter it you'll see the second row in place of the first child.
The text was updated successfully, but these errors were encountered: