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
If someone edits the content of a cell (or custom key) while the table's already sorted by that column, then if we sort by it again sorttable will just reverse or re-reverse the column and not notice that the content has changed. Devices now are probably fast enough to schwartzian the content always and not bother with the "just reverse without looking" optimisation, although we still need to record which direction the table is sorted in anyway so we know to reverse it.
The text was updated successfully, but these errors were encountered:
If someone edits the content of a cell (or custom key) while the table's already sorted by that column, then if we sort by it again sorttable will just reverse or re-reverse the column and not notice that the content has changed. Devices now are probably fast enough to schwartzian the content always and not bother with the "just reverse without looking" optimisation, although we still need to record which direction the table is sorted in anyway so we know to reverse it.
The text was updated successfully, but these errors were encountered: