195832 - Thread icon in heading should reflect sorting order when sorted by thread

Status: RESOLVED EXPIRED

(SeaMonkey :: Themes, enhancement)

Description

[Christian Eyrich]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.4a) Gecko/20030228
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.4a) Gecko/20030228

Sorting order of Mails and News when sorted by Subject, Sender a.s.o. being
reflected by small arrows in the heading.
When sorting Mails and News bei thread there's no indication (no place for an
arrow).

I suggest to support two different icons for ascending and descending sorting. I
guess there's no code to address different icons according to requirements.

Take the current icon as icon (little bubbles upper-left to lower-right) for
descending and a mirror-inverted for asending (little bubbles lower-left to
upper-right) order.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Christian Eyrich]

Theme related issue -> Browser/Themes

It's not true there's no code to reflect the different thread sorting orders.
Two different entries for ascending and descendig treecol.threadColumnHeader do
exist in the themes css (at least classic and modern).

But the same icon is assigned to both entries.

Comment 2

[Christian Eyrich]

Attachment: changes to theme-files

Associated icons see next attachment.

Comment 3

[Christian Eyrich]

Attachment: new icons for changes to theme-files

Comment 4

[Christian Eyrich]

taking

Comment 5

[Mike Cowperthwaite]

FYI: This bug is moving in an opposite direction from that requested 
in bug 219787.

Comment 6

[Mike Fedyk]

(In reply to comment #5)
> FYI: This bug is moving in an opposite direction from that requested 
> in bug 219787.

No it's not, it is requesting a different icon for ascending and descending
thread  order.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420