The default bug view has changed. See this FAQ.

Escaped HTML brackets in Atom feeds display as raw HTML in message window

RESOLVED FIXED

Status

MailNews Core
Feed Reader
RESOLVED FIXED
13 years ago
5 years ago

People

(Reporter: Mike Steinbaugh, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

In the example Atom feed, take a look at the entry entitled "Stylesheet
changes." In the content tag, the entry is properly escaped. The CODE tags
should render as HTML in Thunderbird and do properly. However, the H2 tag inside
the CODE tag should not render as HTML but as a readable HTML tag (escaped
brackets). This is not the case in Thunderbird.

This problem has been confirmed to be specific to Thunderbird and not other
newsreaders.

Reproducible: Always
Steps to Reproduce:
1. Add feed to Thunderbird
2. Double-click on entry containing escaped HTML
3. Voila!

Actual Results:  
The escaped HTML is incorrectly rendered as raw HTML

Expected Results:  
Keep the escaped brackets instead of rendering them. The H2 tag should display
as plain text with a left bracket and right bracket visible to the reader.

Updated

12 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

11 years ago
Hi, 
I have encouter this problem too..

In atom feed title, HTML entities are tranformed .. but xml are not:

    <title type="html"><![CDATA[  &gt;  ]]></title>

gives:

    >

as expected. But

    <title type="html"><![CDATA[  &#62;  ]]></title>

gives:

    &#62
QA Contact: rss

Updated

9 years ago
Assignee: mscott → nobody

Updated

8 years ago
Component: RSS → Feed Reader
Product: Thunderbird → MailNews Core

Comment 2

5 years ago
this has been fixed along the way, as both &#62; and &gt; render correctly in <item> <title>s in Tb16 and likely release as well.  reopen if not.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.