Jannis and I are sprinting on this; we'd like to take a 2nd look at potential
behaviors after a long conversation yesterday. The current solution works, but
I think there's still a lot of room for user confusion.
Plan is to look again at existing sorting implementations (on various
apps/platfor
On Thu, Jun 9, 2011 at 12:45 AM, Luke Plant wrote:
> In the new admin sorting UI, which now supports sorting on multiple
> fields, the behaviour can be described by the following two rules:
>
> 1. If you click on a header, it is made the primary sort field
> (with others moved down the list as n
On Jun 9, 9:45 am, Luke Plant wrote:
> In the new admin sorting UI, which now supports sorting on multiple
> fields, the behaviour can be described by the following two rules:
>
> 1. If you click on a header, it is made the primary sort field
> (with others moved down the list as necessary).
>
In the new admin sorting UI, which now supports sorting on multiple
fields, the behaviour can be described by the following two rules:
1. If you click on a header, it is made the primary sort field
(with others moved down the list as necessary).
2. If you click on a header that was already par
