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 538339 - Should use a nicer invisible-char
Should use a nicer invisible-char
Status: RESOLVED FIXED
Product: krb5-auth-dialog
Classification: Other
Component: general
unspecified
Other All
: Normal trivial
: ---
Assigned To: Christopher Aillon
krb5-auth-dialog-maint
Depends on: 538163
Blocks:
 
 
Reported: 2008-06-14 17:04 UTC by Guido Günther
Modified: 2009-04-24 08:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use more gnomish invisible char (849 bytes, patch)
2008-06-14 17:05 UTC, Guido Günther
needs-work Details | Review
better patch (1.01 KB, patch)
2009-04-23 18:30 UTC, Matthias Clasen
none Details | Review

Description Guido Günther 2008-06-14 17:04:31 UTC
Please describe the problem:
The 'dot' seems more common than the star '*' nowadays for usage in password dialogs. Patch attached.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Guido Günther 2008-06-14 17:05:15 UTC
Created attachment 112738 [details] [review]
Use more gnomish invisible char
Comment 2 Christopher Aillon 2008-06-15 17:58:19 UTC
Comment on attachment 112738 [details] [review]
Use more gnomish invisible char

>+		gtk_widget_set(entry, "invisible-char", 0x25cf, NULL);

No.  Nothing should explicitly set this ever anywhere in GNOME, really.  This should be a GTK+ setting that is done by the system GTK or the user in their .gtkrc, really.  Fedora uses 0x2022, I think Debian uses 0x25cf, and some distros still prefer '*'.  My guess is that there's something in the glade file that sets this, and that line(s) should be removed so it falls back to the OS default.
Comment 3 Guido Günther 2008-06-15 20:02:28 UTC
The point here is, that GtkSecureEntry sets this to '*'. I can set a nicer default there then so distros can still override this via their theme.
Comment 4 Matthias Clasen 2009-04-23 18:30:52 UTC
Created attachment 133202 [details] [review]
better patch

Here is a patch that uses the same character that GTK+ would choose. Applying it shows that the sec entry cannot actually coexist with entries in the same process without warnings, but the warnings are harmless.
Comment 5 Guido Günther 2009-04-24 08:57:40 UTC
I basically used the same trick to get rid of the warning: don't install the "gtk-entry-select-on-focus" but query it from GtkEntry when needed. Patch applied, thanks.