pfSense

Created a PR here:
https://github.com/pfsense/pfsense/pull/4709

I applied this patch and seem to have discovered an issue. With the patch in place, I am able to sort on any of the first three columns and that initially appears to work properly. However, it seems the fourth column (edit/delete) does not follow the sorting of the other columns and remains static. This means that when you attempt to edit one of the tunables after sorting, the edit fields that appear belong to a different tunable than the one you attempted to edit.

Glenn Hall wrote in #note-5:

I applied this patch and seem to have discovered an issue. With the patch in place, I am able to sort on any of the first three columns and that initially appears to work properly. However, it seems the fourth column (edit/delete) does not follow the sorting of the other columns and remains static. This means that when you attempt to edit one of the tunables after sorting, the edit fields that appear belong to a different tunable than the one you attempted to edit.

I can't reproduce this on dev snapshots here. The columns all sort properly, clicking edit on any item edits the expected item and so on. I tried sorting by all three columns (ascending and descending), and each time the action icons were correct.

I just pushed a fix to ensure the tunables are always sorted the same way when editing, deleting, etc. It seems to have fixed this for me, but give it a try when it shows up (commit:bc1322f22ff437a169fae932ce4c9e38286d49e7)

I can confirm the latest patch fixes the issue I was seeing with the older patch and all sorting works properly now. Thank you!