Closed
Bug 954628
Opened 10 years ago
Closed 10 years ago
Chat tooltips should contain the topic
Categories
(Instantbird Graveyard :: Contacts window, enhancement)
Instantbird Graveyard
Contacts window
Tracking
(Not tracked)
RESOLVED
FIXED
1.3
People
(Reporter: clokep, Assigned: benediktp)
Details
(Whiteboard: [1.3-wanted])
Attachments
(1 file)
1.74 KB,
patch
|
clokep
:
review+
|
Details | Diff | Splinter Review |
*** Original post on bio 1196 at 2011-12-07 13:10:00 UTC *** Chat tooltips currently only show the protocol icon and the MUC name, we should include the topic (if one is set), this is especially useful for conversations on hold. I'm not sure if there is other useful information to show in here (# of participants, what your status is in the room?).
Comment 1•10 years ago
|
||
*** Original post on bio 1196 at 2011-12-07 13:15:40 UTC *** maybe whether you have left the conversation or are still in it? maybe the number of unread messages and the number of unread messages targeted to you? (not very useful for conversations on hold, but may be nice for unselected tabs)
Reporter | ||
Updated•10 years ago
|
Whiteboard: [1.3-wanted]
Assignee | ||
Comment 2•10 years ago
|
||
*** Original post on bio 1196 as attmnt 1903 at 2012-09-07 09:17:00 UTC *** This patch adds the topic to the tooltip of conversations.
Attachment #8353661 -
Flags: review?(clokep)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → benediktp
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•10 years ago
|
||
Comment on attachment 8353661 [details] [diff] [review] Patch *** Original change on bio 1196 attmnt 1903 at 2012-09-07 10:29:30 UTC *** This is something I try to do all the time! Looks good, thanks! :)
Attachment #8353661 -
Flags: review?(clokep) → review+
Comment 4•10 years ago
|
||
*** Original post on bio 1196 at 2012-09-13 12:12:04 UTC *** http://hg.instantbird.org/instantbird/rev/879c7827a2e2 I look forward to using an nightly with this!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.3
You need to log in
before you can comment on or make changes to this bug.
Description
•