Opened 10 years ago
Last modified 10 years ago
#12210 new enhancement
Show username and email in tooltip when hovering over a full name
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases | 
| Component: | general | Version: | |
| Severity: | normal | Keywords: | username | 
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When [trac] show_full_names is True the user's full name is shown. The username and email could also be shown in the tooltip when hovering over the full name, like th:UsernameDecoratePlugin does. The email address would be obfuscated or not shown depending on the settings and user permissions.
Attachments (0)
Change History (3)
comment:1 by , 10 years ago
follow-up: 3 comment:2 by , 10 years ago
UsernameDecoratePlugin also has the following features:
- Gravatar, also proposed in #11068, and used on Wordpress Trac site (#11199)
 - Author label can be customized with keys 
$username,$email,$fullname - Author title can be customized with keys 
$username,$email,$fullname 
tipsy is used for the tooltip styling.
Adding customizability for author label and title might be option overload for Trac, but adding a title, and possibly the Gravatar, seem like nice enhancements. It's worth considering for Trac 1.3.x.
With the work done in #7339, we can probably make a simpler version of UsernameDecoratePlugin, assuming we are now using Chrome.authorinfo in all the places that an author needs to be formatted in Trac. Also, Environment.get_known_users is cached (#11868) and can return a dictionary ([14247]). If UsernameDecoratePlugin wasn't adding a Gravatar it wouldn't need to implement ITemplateStreamFilter and could continue to work beyond Trac 1.4 ([th 15213]).
Would there be any objection to having Trac communicate with the Gravatar service? If necessary we could try to implement it through a Component in tracopt.
comment:3 by , 10 years ago
Replying to Ryan J Ollos:
Would there be any objection to having Trac communicate with the Gravatar service? If necessary we could try to implement it through a
Componentintracopt.
If implemented at all, make it optional defaulting to off.
Living in a corporate environment I wouldn't be too happy to have my internal bug tracker communicate with external servers possibly disclosing information about users of the bug tracker.



  
I'll have to look at the code more closely, but presumably the UsernameDecoratePlugin would no longer be needed after this change, and could be listed as obsolete in TracUpgrade.