Closed
Bug 274775
Opened 20 years ago
Closed 20 years ago
Expat accepts invalid namespaces
Categories
(Core :: XML, defect, P3)
Core
XML
Tracking
()
RESOLVED
FIXED
mozilla1.8alpha6
People
(Reporter: peterv, Assigned: peterv)
Details
Attachments
(6 files)
|
150 bytes,
text/xml
|
Details | |
|
165 bytes,
text/xml
|
Details | |
|
174 bytes,
text/xml
|
Details | |
|
164 bytes,
text/xml
|
Details | |
|
162 bytes,
text/xml
|
Details | |
|
6.36 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
There are a two prefixes (xml and xmlns) that have a fixed namespace URI (http://www.w3.org/XML/1998/namespace and http://www.w3.org/2000/xmlns/). These prefixes may not be bound to a different namespace URI and no other prefixes may be bound to those namespace URIs. Expat currently doesn't flag that as an error. See http://www.w3.org/TR/2004/REC-xml-names11-20040204/#xmlReserved and http://sourceforge.net/tracker/index.php?func=detail&aid=695407&group_id=10127&atid=110127
| Assignee | ||
Comment 1•20 years ago
|
||
| Assignee | ||
Comment 2•20 years ago
|
||
| Assignee | ||
Comment 3•20 years ago
|
||
| Assignee | ||
Comment 4•20 years ago
|
||
| Assignee | ||
Comment 5•20 years ago
|
||
| Assignee | ||
Comment 6•20 years ago
|
||
My patch for Expat just got applied to the Expat trunk (http://cvs.sourceforge.net/viewcvs.py/expat/expat/lib/xmlparse.c?r1=1.141&r2=1.143). I backported it to our version of Expat.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.8alpha6
| Assignee | ||
Comment 7•20 years ago
|
||
| Assignee | ||
Updated•20 years ago
|
Attachment #169554 -
Flags: superreview?(jst)
Attachment #169554 -
Flags: review?(jst)
Comment 8•20 years ago
|
||
Comment on attachment 169554 [details] [diff] [review] v1 r+sr=jst
Attachment #169554 -
Flags: superreview?(jst)
Attachment #169554 -
Flags: superreview+
Attachment #169554 -
Flags: review?(jst)
Attachment #169554 -
Flags: review+
| Assignee | ||
Updated•20 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•