W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2012

[whatwg] getValues on PropertyNodeList is now redundant

From: Ojan Vafai <ojan@chromium.org>
Date: Fri, 30 Mar 2012 16:29:12 -0700
Message-ID: <CANMdWTv2m9kvQr6YhAh9JgNFHxHZENX1sdSm9o0c8hE+AAAXzw@mail.gmail.com>
OIC. Sorry, I misread the spec. I rescind.

On Fri, Mar 30, 2012 at 2:59 PM, Erik Arvidsson <arv at chromium.org> wrote:

> I'm not sure. getValues returns an array of the itemValue of the nodes
> in the NodeList. Something that can be trivially implemented as:
>
> PropertyNodeList.prototype.getValues = function() {
>  return this.map(function(node) {
>    return node.itemValue;
>  });
> };
>
> If this is commonly used then it might make sense to keep it so that
> not every application has to duplicate this code.
>
> erik
>
>
>
>
>
>
>
> On Fri, Mar 30, 2012 at 14:21, Ojan Vafai <ojan at chromium.org> wrote:
> >
> http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#propertynodelist
> >
> > DOM4 now has NodeList inherit from Array (see
> >
> http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#interface-nodelist
> ).
> > As such, the getValues function is no longer useful. PropertyNodeList
> > should just be a regular NodeList.
> >
> > Ojan
>
Received on Friday, 30 March 2012 16:29:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC