Closed
Bug 117729
Opened 23 years ago
Closed 15 years ago
Ability to type folder name for filing or goto
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: edemaine, Unassigned)
References
Details
I would like to be able to type in the name of a folder to file an email message
to. Ideally I'd also like to be able to type in the name of a folder to go to
(visit), but this is less important.
Possible user interfaces:
1. A key 's' (save) or 'f' (file) or similar brings up a popup in which I can
enter a folder name (ideally with autocompletion) and then click a 'Move'
button. (Could also have 'Copy' button.) Popup would probably also have a
dropdown selector for the service (which IMAP/POP server you're talking about),
defaulting to the service containing the message being filed.
2. The File dropdown also has a text entry area where I can type the folder name.
Option 2 sounds more difficult to implement, but maybe it's possible. I would
actually prefer Option 1 because it's faster, but the disadvantage of Option 1
is that the feature is hard to find. A hybrid approach is to add a link to the
popup in the File dropdown, and the link mentions the keyboard shortcut. That
way you can find it in the GUI, but can also have fast access.
Rationale: I am used to this feature in Pine, and consequently have over 760
folders, which makes it impractical to sift through the File dropdown or the
folder list.
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 2•21 years ago
|
||
*** Bug 154176 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Updated•17 years ago
|
Assignee: mail → nobody
QA Contact: stephend → message-display
Target Milestone: Future → ---
![]() |
||
Comment 3•16 years ago
|
||
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
Status: NEW → UNCONFIRMED
![]() |
||
Comment 4•15 years ago
|
||
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
You need to log in
before you can comment on or make changes to this bug.
Description
•