Re: [whatwg] Type of PropertyNodeList.contents

2009-08-03 Thread Ian Hickson
On Fri, 24 Jul 2009, Andrew Oakley wrote:

 PropertyNodeList.contents seems to be defined differently in the IDL and
 the text related to it.
 
 The IDL says:
  typedef sequenceany PropertyValueArray;
  
  interface PropertyNodeList : NodeList {
attribute PropertyValueArray contents;
  };
 
 The description says:
  The contents DOM attribute on the PropertyNodeList object, on
  getting, must return a newly constructed DOMStringArray whose values
  are the values obtained from the content DOM property of each of the
  elements represented by the object, in tree order.
 
 DOMStringArray doesn't appear to be defined anywhere, however DOM 3 Core
 has a DOMStringList which seems to have this purpose.
 
 HTMLPropertyCollection.names returns a DOMStringList, so I think we
 should be consistent and also return a DOMStringList for
 PropertyNodeList.contents.

Fixed. It can't be a DOMStringList (nor a DOMStringArray, whatever that 
was supposed to be), because some of the values are going to themselves be 
items, and not strings.

Thanks,
-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


[whatwg] Type of PropertyNodeList.contents

2009-07-24 Thread Andrew Oakley
PropertyNodeList.contents seems to be defined differently in the IDL and
the text related to it.

The IDL says:
 typedef sequenceany PropertyValueArray;
 
 interface PropertyNodeList : NodeList {
   attribute PropertyValueArray contents;
 };

The description says:
 The contents DOM attribute on the PropertyNodeList object, on
 getting, must return a newly constructed DOMStringArray whose values
 are the values obtained from the content DOM property of each of the
 elements represented by the object, in tree order.

DOMStringArray doesn't appear to be defined anywhere, however DOM 3 Core
has a DOMStringList which seems to have this purpose.

HTMLPropertyCollection.names returns a DOMStringList, so I think we
should be consistent and also return a DOMStringList for
PropertyNodeList.contents.

-- 
Andrew Oakley