On 10/19/09 6:30 PM, Jonas Sicking wrote:
In particular I'm wondering what made other vendors decide to support this.
I'd already asked this on this list, back in July. The relevant answers (from the "[whatwg] .tags on HTMLCollections" thread):
On Tue, 14 Jul 2009, Maciej Stachowiak wrote:
Support for HTMLCollection.tags() in WebKit predates the fork from KHTML. So we don't know why it was originally added.
On Tue, 14 Jul 2009, Maciej Stachowiak wrote:
I don't know of a reason it's needed for collections other than document.all. But it also doesn't seem harmful and I can't say definitively whether it helps anything. I wouldn't object to removing it from the spec, but we probably wouldn't remove it from WebKit short of evidence that it's actually harmful. Perhaps Opera people can shed more light on the matter.
On Thu, 23 Jul 2009, Anne van Kesteren wrote:
From what I heard so far it is there because of document.all. If document.all does indeed need to return a separate object as HTML5 suggests we can probably remove it from HTMLCollection in due course.
-Boris
