Closed Bug 954016 Opened 11 years ago Closed 11 years ago

Show whowas information on tooltip for offline IRC buddies

Categories

(Chat Core :: IRC, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 954556

People

(Reporter: benediktp, Unassigned)

References

Details

*** Original post on bio 579 at 2010-11-10 22:52:00 UTC *** The information available from WHOIS should be displayed on tooltips where appropriate: in my opinion that would include the following places: Nicknames in participants list, IRC buddies in the buddy list and the tooltip of private conversation tabs.
Blocks: 954011
*** Original post on bio 579 at 2010-11-11 00:15:24 UTC *** Just a note that for buddies who have since gone offline we can do a "whowas" for that. We should also include a "who" query for what the user supports I believe.
Depends on: 953721
Depends on: 954156
No longer depends on: 953721
*** Original post on bio 579 at 2011-09-05 21:13:24 UTC *** I fixed this in https://hg.instantbird.org/instantbird/rev/6663790446e3 / bug 954156 (bio 721). This bug can either be resolved as a dup of bug 954156 (bio 721), or be changed into a JS-IRC thing to implement the suggestions from comment 1 (I don't think libpurple calls more than "whois" when doing get_info calls).
*** Original post on bio 579 at 2011-09-09 10:17:47 UTC *** Changing this to the whowas situation to not dup bug 954156 (bio 721).
Summary: Show whois information on tooltip for IRC buddies → Show whowas information on tooltip for offline IRC buddies
Severity: normal → enhancement
Component: Other → IRC
OS: Windows XP → All
Product: Instantbird → Chat Core
Hardware: x86 → All
*** Original post on bio 579 at 2012-04-03 12:26:41 UTC *** This should be fixed by a combination of bug 954764 (bio 1332) and bug 954556 (bio 1123).
*** Original post on bio 579 at 2012-04-04 18:34:07 UTC *** As per comment #4, is a duplicate of bug 954556 (bio 1123) now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.