Closed
Bug 793299
Opened 12 years ago
Closed 11 years ago
firefox cannot parse < and > in xml
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: admn, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
1.21 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 Steps to reproduce: am parsing xml containing < and > in a jsp Actual results: am getting parse error But it used work in earlier version of firefox , chrome and explorer Expected results: < and > should ve displayed in UI
Actually i just discovered that it can parse > i.e i can get '>" on the UI but not <('<') SO firefox v15 cannot parse < in xml
Comment 2•12 years ago
|
||
Please provide a testcase, either attached or as URL
Severity: critical → normal
Priority: P5 → --
Dupe of bug 788444?
Comment 4•12 years ago
|
||
Hard to tell given complete lack of steps to reproduce. Parsing < in XML in general works just fine, of course (try data:text/xml,<root><</root>), which is where steps describing _exactly_ what is being done come in.
Adarsh, provide a testcase, please.
Flags: needinfo?(admn)
Keywords: testcase-wanted
The attached html page will help to reproduce the issue mentioned in this bug.
Attachment #724265 -
Attachment mime type: text/plain → text/html
Flags: needinfo?(admn)
Keywords: testcase-wanted → testcase
(In reply to Praveen from comment #6) > Created attachment 724265 [details] > file which help you to reproduce the issue > > The attached html page will help to reproduce the issue mentioned in this > bug. Where is the issue? <subentry value="g1UFT$94AABaaA:Item:001117-Item>:::Item"></subentry> is parsed as <subentry value="g1UFT$94AABaaA:Item:001117-Item>:::Item"></subentry> in the dialog box.
Flags: needinfo?(praveen.kamatnurkar)
Thats the actual issue. I want to send the data to xml parser which in turns gives parsing error. This works perfectly in IE9.
Flags: needinfo?(praveen.kamatnurkar)
Comment 9•11 years ago
|
||
Our current behavior is the behavior the spec calls for. Your problem is that you're sending the output of an _HTML_ serializer to an _XML_ parser. The two languages have different escaping and parsing rules. If you want to serialize as XML, use an XML serializer. See http://domparsing.spec.whatwg.org/#the-xmlserializer-interface for example.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•