Bug 337330

Summary: HTML tags in title are not rendered correctly
Product: [Applications] akregator Reporter: Rolf Eike Beer <kde>
Component: internal browserAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: osterfeld
Priority: NOR    
Version: 4.13.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: CMake commit feed exposing the problem
RSS testcase

Description Rolf Eike Beer 2014-07-10 15:59:28 UTC 
If a feed contains HTML tags (like &lt;) in the title of an article, those tags are not properly rendered. The main problem happens if there is a &lt;something&gt; text inside, this is entirely missing on the screen (probably because it is "rendered" twice, resulting in an invalid (ignored) markup tag.

Reproducible: Always
Comment 1 Rolf Eike Beer 2014-07-10 15:59:55 UTC 
Created attachment 87680 [details]
CMake commit feed exposing the problem
Comment 2 Frank Osterfeld 2014-10-25 17:40:09 UTC 
The attached file is HTML. Do you have an example feed (RSS or atom)?
Comment 3 Rolf Eike Beer 2015-01-11 14:09:57 UTC 
Created attachment 90349 [details]
RSS testcase
Comment 4 Frank Osterfeld 2015-01-18 14:45:58 UTC 
RSS2 can contain both plain text or HTML without any clear identification what's contained. So finding out if the contained <, > constitute a tag is guesswork. To fix this issue, one could try harder to check if the tag is valid ("<lt and>" isn't) or use a whitelist of html tags instead of accepting everything that looks like a tag.
Comment 5 Rolf Eike Beer 2015-01-18 16:59:24 UTC 
The problem arises when I write something in the subject line like "fix <p> tag being handled wrong" or something like that.
Comment 6 Denis Kurz 2016-09-24 19:39:02 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 21:48:48 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.