On Mon, 19 Oct 2009, Jonas Sicking wrote:
I've been meaning to send a formal email on this subject, and with the
recent discussion going on over in the W3C webapps mailing list I
figured now was a good time.
I'd like to formally request that .tags() is removed from the
HTMLCollection
On Thu, Oct 22, 2009 at 5:26 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 19 Oct 2009, Jonas Sicking wrote:
I've been meaning to send a formal email on this subject, and with the
recent discussion going on over in the W3C webapps mailing list I
figured now was a good time.
I'd like to
Hi All,
I've been meaning to send a formal email on this subject, and with the
recent discussion going on over in the W3C webapps mailing list I
figured now was a good time.
I'd like to formally request that .tags() is removed from the
HTMLCollection interface. Unless it can be shown that
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
On Mon, Oct 19, 2009 at 5:01 PM, Boris Zbarsky bzbar...@mit.edu wrote:
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 Fri, 14 Aug 2009, Jonas Sicking wrote:
On Fri, Aug 14, 2009 at 3:35 AM, Ian Hicksoni...@hixie.ch wrote:
On Fri, 7 Aug 2009, Jonas Sicking wrote:
I haven't removed HTMLCollection.tags yet, since it appears to be
implemented by most browsers. If we can get Opera and WebKit to
On Fri, 7 Aug 2009, Jonas Sicking wrote:
I haven't removed HTMLCollection.tags yet, since it appears to be
implemented by most browsers. If we can get Opera and WebKit to remove
support, then I'll remove it from the spec.
Given that we have some data indicating that .tags() is not
On Fri, Aug 14, 2009 at 3:35 AM, Ian Hicksoni...@hixie.ch wrote:
On Fri, 7 Aug 2009, Jonas Sicking wrote:
I haven't removed HTMLCollection.tags yet, since it appears to be
implemented by most browsers. If we can get Opera and WebKit to remove
support, then I'll remove it from the spec.
On Fri, Aug 14, 2009 at 12:02 PM, Jonas Sickingjo...@sicking.cc wrote:
On Fri, Aug 14, 2009 at 3:35 AM, Ian Hicksoni...@hixie.ch wrote:
On Fri, 7 Aug 2009, Jonas Sicking wrote:
I haven't removed HTMLCollection.tags yet, since it appears to be
implemented by most browsers. If we can get
On Tue, Jul 28, 2009 at 2:48 PM, Ian Hicksoni...@hixie.ch wrote:
On Mon, 13 Jul 2009, Boris Zbarsky wrote:
Ian just pointed out to me that his current draft requires
HTMLCollections to implement a tags() method (which seems to do a filter
by tagName on the contents of the collection).
As
On Mon, 13 Jul 2009, Boris Zbarsky wrote:
Ian just pointed out to me that his current draft requires
HTMLCollections to implement a tags() method (which seems to do a filter
by tagName on the contents of the collection).
As far as I can tell, IE, Webkit, and Opera implement this; Gecko
On Fri, 24 Jul 2009 04:56:15 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
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
Anne van Kesteren wrote:
They are indeed distinct, but do share the same interface name in Opera the
moment, as far as I can tell...
Oh, the _name_ is shared in Gecko too. Just not anything else. ;)
In any case, my point was that we'd be ok with removing the tags member from
On Tue, 14 Jul 2009 11:58:30 +0200, Maciej Stachowiak m...@apple.com 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
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.
Given that the namedItem behavior of document.all is different
Ian just pointed out to me that his current draft requires
HTMLCollections to implement a tags() method (which seems to do a filter
by tagName on the contents of the collection).
As far as I can tell, IE, Webkit, and Opera implement this; Gecko does
not. I was wondering whether any of the
On Jul 13, 2009, at 11:55 PM, Boris Zbarsky wrote:
Ian just pointed out to me that his current draft requires
HTMLCollections to implement a tags() method (which seems to do a
filter by tagName on the contents of the collection).
As far as I can tell, IE, Webkit, and Opera implement this;
Maciej Stachowiak wrote:
Support for HTMLCollection.tags() in WebKit predates the fork from
KHTML. So we don't know why it was originally added.
I guess the other question is whether you feel it's worth keeping...
-Boris
On Jul 14, 2009, at 2:50 AM, Boris Zbarsky wrote:
Maciej Stachowiak wrote:
Support for HTMLCollection.tags() in WebKit predates the fork from
KHTML. So we don't know why it was originally added.
I guess the other question is whether you feel it's worth keeping...
I don't know of a reason
19 matches
Mail list logo
