Summary: | Rich text editor now returns <p> elements which are not handled by AIM's parser | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Benson Tsai <btsai> |
Component: | libkopete | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jay |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | one liner patch to fix it |
Description
Benson Tsai
2008-01-07 09:25:28 UTC
Confirmed. I actually introduced the <p> behavior. How silly of me to assume that a peer client might not understand basic HTML. :) Created attachment 22897 [details]
one liner patch to fix it
Please apply this patch and tell me if it fixes the problem on the AIM-client
side, and if it introduces any problems on the Kopete side. I didn't test it at
all, but it should be okay.
That worked. Although, shouldn't <p>content</p> be translated to something along the lines of content<br />? That's not needed, since real newlines in the text editor are reported as <br>. Committed fix. http://websvn.kde.org/?view=rev&revision=758764. Would have closed in commit message but git is confusing me. *** Bug 156529 has been marked as a duplicate of this bug. *** |