Seems to me that when you access a slot that in some sense "doesn't exist" it should return undefined, not null. There are plenty of semantic cases (is this attribute defined but currently unset, or not defined at all) where the difference can be significant. I realize not all languages support the distinction, but JS does and it's actually a useful feature. ss On Tue, Oct 19, 2010 at 11:06 AM, Erik Arvidsson <arv@chromium.org> wrote: > On Tue, Oct 19, 2010 at 09:50, Garrett Smith <dhtmlkitchen@gmail.com> > wrote: > ... > > CSSStyleDeclaration. What about the other "collection" objects? HTML5 > > says that collections are now callable and specifies that "indexed" > > property access on collections returns null. But what about other APIs > > such as NodeList, NamedNodeMap, CSSRuleList, and StyleSheetList? > > Almost all of them are defined to return null. Actually > CSSStyleDeclaration is the only exception I could find in WebCore > sources. > > > Changing the wording for each collection would be painfully > > repetitious, involving a spec author for each spec. There is not any > > super interface collection defined that also defines `item`, > > callability, property access, etc. though if there were then all > > collection type objects inherit from that and would avoid shotgun > > surgery. That would seem to be something for DOM 4 core, if such a > > thing is to be written. > > WebIDL has a section for sequence but it is not fleshed out yet. > > erik > >
Received on Tuesday, 19 October 2010 17:47:53 UTC