Bug 356999 - HTML formatting on incoming messages not being processed
Summary: HTML formatting on incoming messages not being processed
Status: RESOLVED WORKSFORME
Alias: None
Product: telepathy
Classification: Unmaintained
Component: text-ui (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-21 13:30 UTC by rectifier04
Modified: 2022-11-18 05:17 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rectifier04 2015-12-21 13:30:53 UTC
Using chat application version 15.12.0, using XMPP protocol
Any incoming messages from at least Pidgin client show html syntax in chat.
All links show "<a href="LINKHERE">LINKHERE</a>, line breaks, font changes, etc. all show just the HMTL wrapped text on one big line getting word wrapped.
Regular non-formatted messages show fine
Comment 1 rectifier04 2015-12-25 01:47:47 UTC
During normal use I've noticed that html tags aren't being formatted when received using my jabber.org account, but using my jabber.otr.im account things are formatted at least somewhat properly.
jabber.otr.im seems to strip formatting in some way, somehow; indentation and links are fine, but size/color are stripped.
Comment 2 Aranjedeath 2016-04-11 04:17:42 UTC
I can confirm this as well. A friend uses pidgin, and everything he sends comes through as escaped HTML. ampersands are &amp; and the like. 

If he pastes something that has formatting, it keeps the formatting (in HTML), a la <b> <span color="green"></span and so on.

It'd be great to have it fixed :D
Comment 3 Aranjedeath 2016-04-11 04:23:47 UTC
I hate double-posting but none of the bug information is right (as far as platforms). I'm running the latest version in Kubuntu 16.04 (it's in beta or whatever right now), which means "Chat Application" 15.12.1, Kde Frameworks 5.18, Qt 5.5.1.
Comment 4 Justin Zobel 2022-10-19 22:10:55 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-03 05:06:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-11-18 05:17:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!