DOM Level 3 Core Issues List
Individual view
This list received comments from 2 groups and 12 individuals.
Comments from groups
- Internationalization WG
[10 issues ]
- importNode-1 :
adoptNode and importNode [closed]
- arnold-25 :
byte and character offsets [closed]
- yergeau-12 :
actualEncoding and xmlEncoding [closed]
- yergeau-13 :
renameNode and invalid characters [closed]
- yergeau-14 :
normalize() and character normalization [open]
- yergeau-15 :
CharacterData methods and character normalization [open]
- yergeau-16 :
"cdata-sections" default must be false [closed]
- yergeau-17 :
check character normalization? [closed]
- yergeau-18 :
Unicode 4.0 [closed]
- yergeau-19 :
URI/IRIs [open]
- XML Core
[13 issues ]
- aillon-1 :
Document.xmlVersion [open]
- manian-2 :
unspecified standalone [open]
- yergeau-1 :
nodeName? [open]
- yergeau-2 :
Attribute values and entity references [open]
- yergeau-3 :
Entity declarations [open]
- yergeau-4 :
redundant if? [open]
- yergeau-5 :
Namespace algorithm [open]
- yergeau-6 :
actualEncoding vs xmlEncoding [open]
- yergeau-7 :
xmlVersion mapping [open]
- yergeau-8 :
notations mapping [open]
- yergeau-9 :
no namespace and Infoset [open]
- yergeau-10 :
previous and next sibling mapping [open]
- yergeau-11 :
CDATA sections and Infoset [open]
Comments from individuals
- Andrew Clover
[8 issues ]
- clover-1 :
an application data [closed]
- clover-2 :
DOM features and plus (+) sign [closed]
- clover-3 :
renameNode and non-namespace nodes [closed]
- clover-4 :
logically adjacent and wholeText [closed]
- clover-5 :
error types [closed]
- clover-6 :
whitespace-in-element-content [closed]
- clover-7 :
Text.data [closed]
- clover-8 :
DOMError severity [closed]
- Anjana Manian
[3 issues ]
- manian-1 :
getDOMImplementation(s) [open]
- manian-2 :
unspecified standalone [open]
- manian-3 :
whitespaces [open]
- Christopher Aillon
[1 issue ]
- aillon-1 :
Document.xmlVersion [open]
- Curt Arnold
[26 issues ]
- arnold-1 :
NameList: contains and containsNS [closed]
- arnold-2 :
attribute name case [open]
- arnold-3 :
hasFeature and Core 1.0 [closed]
- arnold-4 :
ordered collection [closed]
- arnold-5 :
getName vs getLocalName [open]
- arnold-6 :
exceptions in NameList [closed]
- arnold-7 :
DOMImplementationSource [closed]
- arnold-8 :
actual encoding? [closed]
- arnold-9 :
config or configuration? [closed]
- arnold-10 :
documentURI and valid URIs [closed]
- arnold-11 :
recognized XML encoding [closed]
- arnold-12 :
Requirements of standalone [closed]
- arnold-13 :
adoptNode and importNode [closed]
- arnold-14 :
adoptNode return value [closed]
- arnold-15 :
Attributes and renameNode [closed]
- arnold-16 :
Position comparison [open]
- arnold-17 :
getFeature and hasFeature [closed]
- arnold-18a :
isWhitespaceInElementContent() or isWhitespaceInElementContent ? [open]
- arnold-18 :
isId() or isId ? [open]
- arnold-19 :
DOMError.clone() [closed]
- arnold-20 :
User data and event handling [closed]
- arnold-21 :
anonymous types [closed]
- arnold-22 :
XML Schema and DTD types [open]
- arnold-23 :
nested and anonymous types [open]
- arnold-24 :
handleErrors [closed]
- arnold-25 :
byte and character offsets [closed]
- Darin Adler
[1 issue ]
- adler-1 :
"negative count" and unsigned counts [open]
- Glenn A. Adams
[1 issue ]
- adams-1 :
DOMImplementationRegistry behavior [closed]
- Jeffery B. Rancier
[1 issue ]
- rancier-1 :
iterators for DOMConfiguration [open]
- Johnny Stenback
[1 issue ]
- stenback-1 :
setting Document.prefix [open]
- Petteri Stenius
[1 issue ]
- stenius-1 :
derived types [closed]
- Scott Nichol
[1 issue ]
- nichol-1 :
Node.namespaceURI [open]
- Susan Lesch
[1 issue ]
- lesch-1 :
isWhitespaceInElementContent or isWhiteSpaceInElementContent ? [open]
- Vadim O. Ustiansky
[1 issue ]
- ustiansky-1 :
What exception to raise? [open]
Maintained by DOM Working Group.Last update: $Date: 2004/02/19 16:25:03 $
This page was generated as part of the
Extensible Issue
Tracking System (ExIT)
Copyright © 2003
W3C® (MIT, ERCIM,
Keio), All Rights Reserved. W3C liability, trademark, document
use and software licensing
rules apply. Your interactions with this site are in accordance with
our public and
Member
privacy statements.