Closed Bug 168876 Opened 22 years ago Closed 14 years ago

annoying CANNOT CONNECT TO SERVER window

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: contacto, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910

Whey you are not conected to the internet or are experiencing some problems with
your connection you are several times bugged by popping windows telling you that
it is impossible to connect to server to check mails...

Imagine now you have 8 accounts adjusted to check emails each 2 minutes...

My suggestion is the creation of a small icon of yellow triangle with an
exclamation mark inside, between the pipe and the lock, that would stay black
and white on normal conditions and yellow on error (the icon could blink each
time an error occurrs). 

Now the magic.

All the error information should be logged to a buffer of a limited size.
If you put the mouse over that icon a floating window would appear showing the
last 5 or 6 entries of that log. If you put the mouse out of that icon, that
floating window would close. No click necessary. I think the number of clicks
should be minimized in all windows programs. 

Ok, someone will click the icon. For that case, that floating log window would
appear and a scroll bar would be available, to one scroll thru the log and see
what's going on...

I think this will definetively kick those annoying windows out of mozilla.

I think other errors should also be logged instead of showing pop alerts. Ok,
put an option on the preferences, so users can choose between annoying pop up
alerts and cool logging errors...  

:-)


Reproducible: Always

Steps to Reproduce:
1.it is not a bug
2.
3.
QA Contact: gayatri → yulian
Seems like a reasonable request; confirming.  Not a back end component; maybe
front end?
Status: UNCONFIRMED → NEW
Component: Mail Back End → Mail Window Front End
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
this should not only apply for "cannot connect", but also for
-"database error" (common with freemail.web.de, the most-spread free-mail
service in germany)
- "Pass command did not succeed" (common, because many fee-mail services limit
the frequency of checking pop3 accounts)
- the really annoying "cannot proceed while folder is in use" (or similar),
which happens when you are reading mails in your inbox (what is that good for at
all? thunderbird cannot display a message AND check a pop account simultaneously?)

Happening with Thunderbird of 2003/04/23
Product: Browser → Seamonkey
Assignee: mscott → nobody
QA Contact: yulian → message-display
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
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: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.