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

2009-10-21 Thread Brian Kardell
@deprecated ? :) On Tue, Oct 20, 2009 at 8:22 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Wed, Oct 21, 2009 at 4:15 PM, Maciej Stachowiak m...@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

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

2009-10-21 Thread Brian Kardell
In this particular case, I think anything that's implemented in all of the major browser engines should be an official standard, not just de facto. Why only in this particular case? :) As a rule that seems like sound guidance. If it's implemented everywhere, shouldn't you have to make a

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

2009-10-20 Thread Maciej Stachowiak
On Oct 18, 2009, at 4:14 AM, Jonas Sicking wrote: On Sun, Oct 18, 2009 at 12:12 AM, Doug Schepers schep...@w3.org wrote: So, rather than dwell on an admittedly imperfect spec, I personally suggest that we urge WebKit developers to implement .children and .children.length, in the

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

2009-10-20 Thread Robert O'Callahan
On Wed, Oct 21, 2009 at 4:15 PM, Maciej Stachowiak m...@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

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

2009-10-20 Thread Maciej Stachowiak
On Oct 20, 2009, at 8:22 PM, Robert O'Callahan wrote: On Wed, Oct 21, 2009 at 4:15 PM, Maciej Stachowiak m...@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

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

2009-10-18 Thread Doug Schepers
Hi, Garrett- Garrett Smith wrote (on 10/17/09 11:06 PM): It has been so long that I cannot remember (over 8 years since I even tried using that). It is a useless, pointless method that tells little about the result of calling, say: getAttribute(checked). I read Nicholas was struggling with

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

2009-10-18 Thread Jonas Sicking
On Sun, Oct 18, 2009 at 12:12 AM, Doug Schepers schep...@w3.org wrote: So, rather than dwell on an admittedly imperfect spec, I personally suggest that we urge WebKit developers to implement .children and .children.length, in the anticipation that this will be in a future spec but can be useful