After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 306925 - Alert message during automatic email checking not HIG2.0 Compliant
Alert message during automatic email checking not HIG2.0 Compliant
Status: RESOLVED DUPLICATE of bug 247373
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-06-08 17:08 UTC by Lakin Wecker
Modified: 2005-06-08 23:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Lakin Wecker 2005-06-08 17:08:16 UTC 
From chapter 3 of the HIG 2.0 guidelines
http://developer.gnome.org/projects/gup/hig/2.0/windows-alert.html:

"Display an error alert when a user-requested operation cannot be sucessfully
completed. Present errors caused by operations not requested by the user by
another means, unless the error could result in data loss or other serious
problems. For example, an error encountered during an email check initiated by
the user clicking a toolbar button should present an error alert. However, an
error encountered in an automated periodic email check would more appropriately
report failure with a statusbar message."

I have my email set up to check email every minute, and if there happens to be a
problem during the automatic email checking procedure I don't want an alert
popped up, as happens currently.

Steps to reproduce:
Open Evolution.
Disable network connection.
Wait until automatic mail checking is performed.
Observe the alert which is shown.



Other information:
Comment 1 André Klapper 2005-06-08 23:23:14 UTC 
i'm going to mark this as a duplicate of bug 247373, and i've copied your 
comments there - please submit further suggestions and comments to bug 247373 - 
thanks for reporting... :-)

*** This bug has been marked as a duplicate of 247373 ***