Closed Bug 1872 Opened 26 years ago Closed 25 years ago

case insensitivity in xml parsing

Categories

(Core :: DOM: HTML Parser, defect, P2)

x86
Windows 98
defect

Tracking

()

VERIFIED FIXED

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>
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
Status: NEW → ASSIGNED
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).
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Expat was added for M4 by Nisheeth.
Status: RESOLVED → VERIFIED
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.