Closed Bug 77292 Opened 24 years ago Closed 15 years ago

search is styling the results

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: sspitzer, Unassigned)

Details

something to log as a bug, 4.x didn't show the "status" column (stephend's has a patch addresses that, in another bug) but, search uses the rules in threadPane.css, which include rules to change the color and style of the text based on the status. 4.x didn't bold unread messages in the search results. should 6.x search results be uniform, or should they be styled like in the thread pane? since you won't be able to change the status, and you can't view the status, we should not style (in this case bold) unread messages in the search dialog. I'd argue that we should leave the priority styles, as we are still show priority. comments?
sounds good.
Why shouldn't they be styled? If I'm searching for a particular message, I'm quite likely to be searching for a message which I've read (that's why I know it exists to be searched for in the first place). So indicating whether found messages are read or unread is very useful in telling which is the message I was looking for.
mpt, thanks for the comments. The more I think about it, either way works for me. I'm no UI guru, perhaps there was a reason why 4.x did what it did? I'm not sure what other mail programs do. since it won't be fixed any time soon, we can discuss the decision.
I don't have a problem with the search results being displayed styled and agree it would be useful to some users. I think 4.x didn't style them because of the issue of what happens if the user then opens/reads one of the "unread" messages from the search result. So 4.x just choose to avoid the issue. So, if we do show styled headers in the Search results: 1. Is the "Read/Unread" column available (but not shown by default) in Search? 2. If the user opens/reads one of the "unread" messages from the search results does it become "unread" in the Search results AND in other windows? 3. If the user changes read/unread state of the message using the column "green star" icon, does the state change in other windows as well. I would think the answer to the questions about would be yes.
reassigning to naving
Assignee: gayatrib → naving
mass re-assign.
Assignee: naving → sspitzer
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search
Assignee: mail → nobody
QA Contact: search → message-display
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
Status: NEW → UNCONFIRMED
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
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
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
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
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
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
Search results should be styled like the normal threadpane (in fact, I don't even know why was a different window in the first place)...
Resolution: EXPIRED → WONTFIX
You need to log in before you can comment on or make changes to this bug.