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 710396 - no feedback on nick change
no feedback on nick change
Status: RESOLVED OBSOLETE
Product: polari
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks: 760854
 
 
Reported: 2013-10-17 15:17 UTC by William Jon McCann
Modified: 2021-06-10 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description William Jon McCann 2013-10-17 15:17:23 UTC
When I type in the nick field to change it I don't get any feedback that something is happening.

Perhaps we can:

 * Make the field insensitive
 * Show a spinner
 * Make field sensitive again
 * Indicate failure with an app-notification
 * Indicate success with an app notification "You are now known as mccann [undo]"
Comment 1 Florian Müllner 2013-10-17 16:16:44 UTC
(In reply to comment #0)
>  * Indicate failure with an app-notification

This is surprisingly hard :-(
The nickname is made up of two separate properties - a local how-I-appear-to-myself one, and an external one synchronized with the server. When setting the nickname, tp will first try to modify the former and then synchronize the second one, but only failing the former is considered an error. There is currently an ugly workaround in place to somehow make it work as expected, but this will need addressing on the tp level imho.


>  * Indicate success with an app notification "You are now known as mccann
> [undo]"

We already show this in-line in the chat log (as any other status messages) - should we keep this if the information is already presented elsewhere more prominently (but less persistent)?
Comment 2 André Klapper 2021-06-10 11:05:35 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Polari, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/polari/-/issues/

Thank you for your understanding and your help.