Closed Bug 356739 Opened 19 years ago Closed 19 years ago

Atom CDATA handling wrong

Categories

(Firefox Graveyard :: RSS Discovery and Preview, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gsnedders, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418.9 (KHTML, like Gecko) Safari/419.3 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-GB; rv:1.8.1) Gecko/20061003 Firefox/2.0 When you have something like "<![CDATA[&amp;]]>amp;" (I'll attach a test case for this bug with more than just that), Firefox display "&amp;", when surely because of the CDATA section it should be displaying "&amp;amp;". Reproducible: Always Steps to Reproduce: 1. Open a feed with such an CDATA section 2. View. Actual Results: Firefox displays "&amp;" Expected Results: Firefox should display "&amp;amp"
Attached file Test case for the bug
I hope this is alright as a test case…
<title type="html"> translates as "what your XML parser outputs is HTML source, ready to be passed off to an HTML parser just as it is." If you have a web page that includes what the XML parser emits, "&amp;amp;", then the display will be just the "&amp;" we display for that feed title. On the other hand, if you change to <title type="text">, saying "what your XML parser outputs is plain text, which must be suitably escaped if you hand it to an HTML parser," then we do display "&amp;amp;" as we then should.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Duh. I go away from dealing with XML for a couple of months and come back thinking that what's in a CDATA section is what's meant to be displayed to the user, not that it's nothing more complex than just not decoding entities within the XML parser (within the CDATA section).
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: