Closed
Bug 217948
Opened 21 years ago
Closed 19 years ago
Yes / no option missing in "advance to next unread message" dialog
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: salfner, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 In the dialog "Advance to next unread message in ..." there are only two choices: - OK, which goes to the next unread message - Cancel, which terminates the dialog and does not lead to the next message. There is no way to get to the next read message! (Or there is a way but it is not at all intuitive and I didn't find it yet ...) In my opinion, there should be 3 buttons: Yes, No and Cancel. Reproducible: Always Steps to Reproduce: 1. Click on the "next" button 2. Try to go the next read message in the current folder 3.
Comment 1•21 years ago
|
||
@reporter: I don't see where there is a bug. The button next (and the keyboard shortcut N) goes to the next unread message. (I grew up with this meaning of "Next" and nobody whants to change this) If you want to go to the next message in your folder (unread or not) you should use the keyboard shortcut F (or Go -> Next -> Message for mouse users) If this is not what you want then please specify more clearly what you expect.
Reporter | ||
Comment 2•21 years ago
|
||
My intuitive understanding of a button called "next" is the next message. If there are no more unread messages, a dialog box (with checkbox "remember my decision") should come up and ask me whether I'd like to read more unread messages in another folder or if I want to continue with read messages in the actual folder. Especially if there are no unread messages (for example in the sent folder) it makes no sense that the next button immediately leads to reading of another folder! In my opinion, clicking on Go -> Next -> Message are too many clicks. Another solution would be to add a little triangle to the next button where I have the option of going to the next message or next unread message.
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 143970 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•21 years ago
|
||
This is not a duplicate of bug 143970! I don't want to add a "don't ask me again" option. I want to add a "... or go to next *read* message in same folder" option if there are no more unread messages in the actual folder!
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 5•19 years ago
|
||
I think this has viability as a preference.
Updated•19 years ago
|
Assignee: sspitzer → mail
Comment 6•19 years ago
|
||
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/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•