This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 535 - Interpretation of datatype-normalization
Summary: Interpretation of datatype-normalization
Status: RESOLVED DUPLICATE of bug 568
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-18 12:29 UTC by nnissar
Modified: 2004-02-24 03:50 UTC (History)
0 users

See Also:

Attachments

Description nnissar 2004-02-18 12:29:14 UTC 
Indexing error of element in NodeList. When the element at index 1 of 
the 'elemList' NodeList is retrieved, getAttribute on the attributes of this 
node should return 0 and 1, and the text content of this node is 0 1 0.
Comment 1 Curt Arnold 2004-02-19 16:36:01 UTC 
The test (and the other datatypenormalization tests) reflects my (possibly 
erroneous) interpretation of 'datatype-normalization' was that values would be 
converted to the canonical form for their values as defined by the XML schema 
spec.  In this case, though the source document had 0 and 1's, they would be 
converted to their canonical form of true and false.  

Regardless of the proper interpretation of 'datatype-normalization', the 
description could be more explicit.
Comment 2 Curt Arnold 2004-02-23 22:50:30 UTC 

*** This bug has been marked as a duplicate of 568 ***