GNOME Bugzilla – Bug 687213
Connection failed notifications
Last modified: 2013-01-16 10:14:20 UTC
I see a lot of the "Connection to <foo> failed" notifications. I'm really not sure why, but I think that bug 652546 is part of it. Anyway, there's a bunch of issues with these notifications (see the attached screneshot): * It isn't clear that the notification is coming from Empathy * It would probably be more meaningful to mention the service provider rather than the address (eg. "Google Talk" instead of "foo@gmail.com") * "Network error" is totally unhelpful * The reconnect button isn't going to help in many cases, and it dismisses the notification, which leaves the user in limbo * "Edit account" should be "Edit Account" * "Connection to <foo> failed" is rather unfriendly
Created attachment 227650 [details] mockup Here's a design proposal for amending the connection failed notifications. Some of the changes: * Uses the Empathy icon rather than the error one * Has a friendlier title * Doesn't include the problematic reconnect button * "Edit account" is renamed to "View Account"; this seems a bit nicer, since it doesn't imply that the user is required to make changes - they might just want to check what's going on There's also a mockup here for the wrong password case, which should probably have its own notification.
Those notifications are handled by gnome-shell, not empathy, and I have a patch somewhere to implement the design. Let me attach it...
Created attachment 229527 [details] [review] Telepathy: consolidate and improve connection notifications Use the empathy icon and name instead of the error icon, use a friendlier title and remove the Reconnect button.
Uhm... committed by mistake?
(In reply to comment #4) > Uhm... committed by mistake? What's happening here, Giovanni? Did the patch land?
(In reply to comment #5) > (In reply to comment #4) > > Uhm... committed by mistake? > > What's happening here, Giovanni? Did the patch land? You committed this one month ago, probably by mistake, nobody complained. I'm inclined to say this is fixed.
Eek. OK... :)