New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting arrows are backwards for "standard" convention #596
Comments
+1 on reversing them from where they are right now :) |
+1 for whatever makes sense to you. I can live with both |
+1 to reverse them, if we use icons such as in the FontAwesome link or have some other visual indicator of sort order. According to the UX link, about half of the time users interpreted "up" from "down" differently, meaning that humans don't actually have any shared intuition about this. (I am suddenly reminded of the Dress.) To me this means that having some indication of what the interface means by "up" and "down" is important. Even if we do not decide to include icons which help indicate order, we should probably change the icons anyway so that long-term users have a visual cue that something is different and don't just end up frustrated because things have flipped and they don't know why things seem broken until they figure out the change. |
@shane-kerr totally agree on all counts, I'd be for icons. I couldn't figure out which way they were "supposed" to be, which is what prompted me looking it up. |
better icons for column sorting indication (#596) See merge request gh/peeringdb/peeringdb!45
* Add text to https://peeringdb.com/suggest/fac (#554) * Make LAN information, Website and technical email mandatory for adding an IXP (#291) * Bypass ACK question when at superuser level (#507) * better icons for column sorting indication (#596)
I found some reference to it at https://ux.stackexchange.com/questions/2041/i-want-to-let-the-user-toggle-a-column-heading-to-sort-a-grid-by-a-date-field-h
And, since this is clearly a bikeshed issue, we could also use the icons from FortAwesome/Font-Awesome#9464 :)
The text was updated successfully, but these errors were encountered: