W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2009

Re: childElements, childElementCount, and children (was: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?)

From: Brian Kardell <bkardell@gmail.com>
Date: Tue, 20 Oct 2009 20:38:13 -0700
Message-ID: <8fcaeb2c0910202038x47914c07n5a179ea5318ffceb@mail.gmail.com>
To: robert@ocallahan.org
Cc: Maciej Stachowiak <mjs@apple.com>, Jonas Sicking <jonas@sicking.cc>, Doug Schepers <schepers@w3.org>, WebApps WG <public-webapps@w3.org>, "www-dom@w3.org list" <www-dom@w3.org>
@deprecated ? :)

On Tue, Oct 20, 2009 at 8:22 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Wed, Oct 21, 2009 at 4:15 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>> I agree. The reason I phrased it as I did was to contrast with my previous
>> remarks. The "children" attribute should be part of a standard, even though
>> it creates what I think is a poor design pattern (mix of previous/next and
>> indexed access to the same collection).
> It might be worth adding annotations to the spec to say "this API is
> terrible, do not use" and "this API is terrible, do not follow its design".
> Rob
> --
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
> 53:5-6]
Received on Wednesday, 21 October 2009 12:21:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:15 UTC