Tiny issues (non-critical):
1. If the table has no rows, and thus only table headers
are presented, it is still possible to sort, and thus to
have sorting indicators presented in the headers. I think
it would be more logical to disable sorting if the table
does not contain any rows.
2. If the table is filled with a number of rows, and if the
table is sorted on (let's say) the first column, and if the
first field is editable, then it is possible to have a
situation where the sorting indicator says "sorted
ascending (or decending)" whereas the rows are not in
reality sorted anymore, since the user changed a value
in the first column after having sorted on the first
column. This could be solved in two manners:
a. if a value in a sorted column is changed by the user,
then remove the sorted indicator in the table header
column.
b. OR if a value in a sorted column is changed by the
user, then resort the table based on the newly changed
value.
Selecting between a or b is just a developer choice.
Both a and b prevent a situation where a sorting
indicator is set, not matching the order of rows.
Tom