Closed Bug 243121 Opened 22 years ago Closed 19 years ago

go to next/previous message within search results

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 95140

People

(Reporter: jay, Assigned: mscott)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: version 0.6b (20040427) If you search for a message with Tools | Search Messages, double-click a message to open it, and select Go | Next message, the next message in that mailbox is displayed, rather than the next message in the search results. Reproducible: Always Steps to Reproduce: 1. Select Tools | Search Messages 2. Enter a search phrase 3. Double-click a result to open it 4. Select Go | Next Message
This also occurs as part of deleting the message after opened.
I notice that the "product" on this is Thunderbird. I want to report the same thing for standard Mozilla mail. Do I need to submit a separate bug with a different product name? Or will this bug automagically be applied to Mozilla mail also? Somewhat related is the behavior that at least in Mozilla, the Next button takes you to the next unread message of that folder, rather than just the next message. It will skip to a subsequent folder if there are no more unread messages.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
I can confirm this erroneous behavior on Thunderbird 1.5 beta 1.
Bug 258371 should provide some relief, in case this capability doesn't develop (In reply to Mark's comment #2) > I notice that the "product" on this is Thunderbird. I want to report the same > thing for standard Mozilla mail. Do I need to submit a separate bug with a > different product name? Or will this bug automagically be applied to Mozilla > mail also? no and no - but watching this bug should be sufficient
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Next/previous in search results acts in wrong context → go to next/previous message within search results
> (In reply to Mark's comment #2) > > I notice that the "product" on this is Thunderbird. I want to report the same > > thing for standard Mozilla mail. Do I need to submit a separate bug with a > > different product name? Or will this bug automagically be applied to Mozilla > > mail also? > > no and no - but watching this bug should be sufficient bug 95140 for Seamonkey/suite bug
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Blocks: 262012
(In reply to comment #6) > bug 95140 for Seamonkey/suite bug Now Core. *** This bug has been marked as a duplicate of 95140 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Re above's "If you can still reproduce this problem in the latest version of the product ... please visit the URL of this bug (given at the top of this mail) and add a comment to that effect", I can reproduce this in 2.0.0.19.
You need to log in before you can comment on or make changes to this bug.