After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 86371 - Name and type listing order indicators are upside-down
Name and type listing order indicators are upside-down
Status: RESOLVED DUPLICATE of bug 88585
Product: nautilus
Classification: Core
Component: Views: List View
0.x.x [obsolete]
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-24 17:40 UTC by Braden
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Braden 2002-06-24 17:40:15 UTC
Nautilus is using a down arrow to indicate ascending order, and an up arrow
to indicate descending order. That's backwards.
Comment 1 Dave Bordoley [Not Reading Bug Mail] 2002-06-24 18:21:19 UTC
Is this a gtk tree view bug or nautilus specific? 
Comment 2 Braden 2002-07-01 14:35:21 UTC
Looks like a GTK bug...
Comment 3 Jonathan Blandford 2002-07-26 19:44:41 UTC
This is the correct behavior.

The arrow points in the ascending fashion in the order in which the
list is read (in this case top to bottom).  The list [1, 2, 3, 4, 5]
is clearly ascending, and when we display it in a top to bottom
direction, we want to keep this property.
Comment 4 Braden 2002-07-26 20:02:33 UTC
I think I was mistaken in marking this as a GTK2 bug. I believe it is
in fact a Nautilus bug. Examining this further...

The arrows are oriented correctly for the columns size and date. They
are incorrectly inverted for the columns name and type.
Comment 5 Braden 2002-07-30 22:30:47 UTC
The same problem is occuring in the alphabetically ordered columns of
the Music view.
Comment 6 Dave Bordoley [Not Reading Bug Mail] 2002-08-22 20:21:52 UTC
marking as a dupe of 88585 since that bug has wipro and sun hackers 
ccd and louie triaged it too...

*** This bug has been marked as a duplicate of 88585 ***