Bug 119945 - Messages with rich-text attributes should not be highlighted
Summary: Messages with rich-text attributes should not be highlighted
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: libkopete (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-11 22:19 UTC by Joseph Campbell
Modified: 2007-07-09 09:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Campbell 2006-01-11 22:19:27 UTC
Version:           0.11.0 (using KDE KDE 3.4.3)
Installed from:    SuSE RPMs
OS:                Linux

I have a friend that uses AIM and has his messages set to have a bluish background with white text.  When I use other instant messaging tools (Trillian) I see the highlighting, or change in background color.  Kopete appears to be ignoring the change in color and displaying white text on a white background.

This problem has been observed in RPM versions for suse (0.10.1 through 0.10.3) and a compiled version of the 0.11.0 from SVN.  I would assume this was also present in earlier versions.
Comment 1 Matt Rogers 2006-01-31 04:39:24 UTC
Sounds like our highlighting clashes with some other rich text properties of the message.
Comment 2 Olivier Goffart 2006-03-11 10:48:25 UTC
You should check the case  
"do not show user colors" 
in the color tab of the appearence config
Comment 3 Joseph Campbell 2006-03-13 15:11:45 UTC
I tried every combination of the following check boxes that was found in the appearance dialog on the tab 'Colors & Fonts':

Do not show user specified background color
Do not show user specified foreground color
Do not show user specified rich text

However this one individuals chat text still shows up white on white despite that not being what he intended - and most certainly not what I intend.  Other thoughts?
Comment 4 Olivier Goffart 2006-04-15 10:46:36 UTC
Fixed in 0.12
Comment 5 Amy Brodzik 2007-07-09 09:14:20 UTC
Fixed? I'm still having this problem in Kopete 0.12.5.