Closed Bug 243659 Opened 21 years ago Closed 16 years ago

RFE: Use "Opening folder XYZ..." instead of just "Opening folder..." in status bar.

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 108702

People

(Reporter: mozilla-bugs, Unassigned)

Details

It would be nice if the status bar of the MailNews window would give the _name_ of the folder it is opening as opposed to just "Opening folder..." it prints now (2004050518, 1.7 branch), This would be especially helpful in the case a folder is opened during the downloading of mail for offline - it this case user has no clude which folder is being opened, and it would be nice to have at least "Opening folder XXX..." or even "Opening folder XXX (nn out of nnn)..." to give a better feedback on the progress of the mail download process.
Product: Browser → Seamonkey
Related to/duplicate of bug 108702?
Assignee: sspitzer → mail
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
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.