DOM operations only raise exceptions in "exceptional" circumstances, i.e.,
when an operation is impossible to perform (either for logical reasons,
because data is lost, or because the implementation has become unstable).
In general, DOM methods return specific error values in ordinary
processing situations, such as out-of-bound errors when using
NodeList.
Implementations should raise other exceptions under other circumstances.
For example, implementations should raise an implementation-dependent
exception if a null argument is passed.
Some languages and object systems do not support the concept of
exceptions. For such systems, error conditions may be indicated using
native error reporting mechanisms. For some bindings, for example,
methods may return error codes similar to those listed in the
corresponding method descriptions.
If index or size is negative, or greater than the allowed value
INUSE_ATTRIBUTE_ERR
final public static short INUSE_ATTRIBUTE_ERR(Code)
If an attempt is made to add an attribute that is already in use
elsewhere
INVALID_ACCESS_ERR
final public static short INVALID_ACCESS_ERR(Code)
If a parameter or an operation is not supported by the underlying
object.
since: DOM Level 2
INVALID_CHARACTER_ERR
final public static short INVALID_CHARACTER_ERR(Code)
If an invalid or illegal character is specified, such as in a name. See
production 2 in the XML specification for the definition of a legal
character, and production 5 for the definition of a legal name
character.
INVALID_MODIFICATION_ERR
final public static short INVALID_MODIFICATION_ERR(Code)
If an attempt is made to modify the type of the underlying object.
since: DOM Level 2