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 511953 - wrong focus of "Custom Notification" dialog
wrong focus of "Custom Notification" dialog
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Milan Crha
Evolution QA team
: 272963 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-25 02:47 UTC by André Klapper
Modified: 2008-04-25 08:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed evo patch (1.73 KB, patch)
2008-03-18 14:07 UTC, Milan Crha
committed Details | Review

Description André Klapper 2008-01-25 02:47:33 UTC
1) add a bogus groupwise account
2) right click on the account name in the left pane in the mailer
3) choose "New _Shared Folder..."
4) enter any folder name and choose a folder, click "Create".
5) see the ugly dialog that has resize problems (bug 511950).
6) click "Contacts".
7) add a contact and click "close".
8) click "C_ustomize notification message"
the new "Custom Notification" dialog is displayed BEHIND the "User" dialog.
Comment 1 André Klapper 2008-01-25 02:56:23 UTC
also see bug 511950, bug 511952, bug 511953, bug 511956, bug 511957.
Comment 2 Matthew Barnes 2008-03-11 00:35:36 UTC
Bumping version to a stable release.
Comment 3 Milan Crha 2008-03-18 14:07:06 UTC
Created attachment 107533 [details] [review]
proposed evo patch

for evolution;

There was couple of runtime warnings on the console too.
Comment 4 Srinivasa Ragavan 2008-03-27 09:03:17 UTC
Commit to stable/trunk.
Comment 5 Milan Crha 2008-03-27 11:22:27 UTC
Committed to trunk. Committed revision 35266.
Committed to gnome-2-22. Committed revision 35267.
Comment 6 Milan Crha 2008-04-25 08:23:20 UTC
*** Bug 272963 has been marked as a duplicate of this bug. ***