case insensitivity in xml parsing

VERIFIED FIXED in M4

Status

()

Core
HTML: Parser
P2
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: gdavis, Assigned: vidur (gone))

Tracking

Trunk
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
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

19 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

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

19 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 3

19 years ago
Setting all current Open/Normal to M4.

Comment 4

19 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

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

19 years ago
Expat was added for M4 by Nisheeth.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 6

19 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.