Closed
Bug 1872
Opened 26 years ago
Closed 26 years ago
case insensitivity in xml parsing
Categories
(Core :: DOM: HTML Parser, defect, P2)
Tracking
()
VERIFIED
FIXED
M4
People
(Reporter: gdavis, Assigned: vidur)
Details
The w3c xml spec calls for xml tagging to be case sensitive. Currently gecko is
allowing illegal xml tagging such as <contentarea></ContentArea>
Comment 1•26 years ago
|
||
Adding Vidur to cc: list. All of these XML bugs are duplicates of the "expat is
not being used yet" bug. Vidur, is that being tracked under a separate bug
number? If not, this or #1873 should be used to track it.
Assignee: rickg → vidur
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•26 years ago
|
||
Technically Rickg owns this bug. I know he's working with James Clark to get
expat into our XML parsing process. We also need to propagate errors to the sink
and report them correctly. Finally, we need to not uppercase elements in the
sink (we're currently doing so because the CSS style system requires it).
Comment 4•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•26 years ago
|
||
Expat was added for M4 by Nisheeth.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•26 years ago
|
||
Testing on 6/16 Apprunner using the following small test:
<?xml version="1.0"?>
<test>
<item>one</item>
<item>two</item>
<item>three</item>
</Test>
Parser caught the illegal tagging. Verifying bug fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•