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
With some specific contents of Notes, sorting by Notes column on All Notes view behaves erratically.
This is example of Notes that can be used to reproduce the problem: pagenotes.csv
When I sort by Notes column the first time, no sorting happens (only the sorting arrow at the heading changes):
When I click the Notes heading the second time, the list order is reversed, but it is still not sorted (at least not by any criteria I can identify):
When I click the Notes heading the third time, nothing happens (except for reverting the direction of the arrow):
When I click the Notes heading the fourth time, I get back to the first state.
Interestingly, when I remove dashes from the Notes ("20220125 aaa", etc), the sorting works as expected.
I've tried it with various Regional settings in Windows (including US English), but it does not seem affect the behavior.
Thanks for looking into this. And mainly thanks for the extension!
The text was updated successfully, but these errors were encountered:
With some specific contents of Notes, sorting by Notes column on All Notes view behaves erratically.
This is example of Notes that can be used to reproduce the problem: pagenotes.csv
When I sort by Notes column the first time, no sorting happens (only the sorting arrow at the heading changes):
When I click the Notes heading the second time, the list order is reversed, but it is still not sorted (at least not by any criteria I can identify):
When I click the Notes heading the third time, nothing happens (except for reverting the direction of the arrow):
When I click the Notes heading the fourth time, I get back to the first state.
Interestingly, when I remove dashes from the Notes ("20220125 aaa", etc), the sorting works as expected.
I've tried it with various Regional settings in Windows (including US English), but it does not seem affect the behavior.
Thanks for looking into this. And mainly thanks for the extension!
The text was updated successfully, but these errors were encountered: