W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2002

Re: DOM Level 2 HTML in Last Call

From: Thomas Much <thomas@snailshell.de>
Date: Fri, 15 Feb 2002 00:16:00 +0100
To: Philippe Le Hegaret <plh@w3.org>
CC: WWW DOM <www-dom@w3.org>
Message-ID: <B8920393.B187%thomas@snailshell.de>
am 11.02.2002 20:27 Uhr schrieb Philippe Le Hegaret unter plh@w3.org:

>> In HTMLTableElement there are tFoot, tHead and caption.
>> Why are they *not* readonly?
> 
> You can always remove the elements in the table by using the removeNode
> methods. It doesn't seem necessary to make them readonly without a
> rational and these attributes are already readwrite in implementations.
> 
> The decision was not to accept the requested changes.

That's OK for this question, but IMHO there are still two questions
unresolved:


[again setting tFoot, tHead and caption]
> DOM2-HTML should specify what happens if one tries to assign a wrong
> element type ("raises DOMException on setting, if a wrong element is
> assigned").
(Message-ID: <B847DCA1.9AEF%thomas@snailshell.de>)

Mozilla 0.9.8 throws a conversion error in this case.


> HTMLSelectElement.add raises a DOMException(NOT_FOUND_ERR) if the "before"
> argument is not a descendant of the SELECT element. OK.
> 
> But what happens if I try to add an element (passed in the "element"
> argument), that is not an OPTION element? Currently, add is directly delegated
> to Node.appendChild or Node.insertBefore - that is, I can add HEAD, IMG, FORM
> elements to the options array... That makes no sense.
> 
> If the standard specifies a special operation for adding OPTIONs, it should
> deal with errors specially and raise an exception if an element other than
> OPTION is passed.
(Message-ID: <B847DF6C.9AEF%thomas@snailshell.de>)

MSIE 5.1.3 (Mac) throws a "type mismatch" error in this case.

bye, Thomas
Received on Thursday, 14 February 2002 18:16:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:55 GMT