W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2014

Re: Change to Attr interface in light of XPath

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 18 Feb 2014 09:20:56 -0800
Message-ID: <CA+c2ei8EK5gRwF3nCN+_xctXUe_XW5pJ1Yn9gzvasq0yqZzhpA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: DOM public list <www-dom@w3.org>
On Tue, Feb 18, 2014 at 9:15 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 2/17/14 4:38 PM, Justin Summerlin wrote:
>> This is somewhat problematic since accessing
>> the parent element is needed for our use.
> Exposing a .parentNode on Attr (returning the element it came from) does not
> require all the other Node baggage (child nodes, etc, etc).
> If there are use cases for a .parentNode, as here, exposing it seems fine.

attributenode.parentNode has always returned null. In all versions of
the spec and in all implementations. What you want is
attributenode.ownerElement. I'm surprised that it's been removed from
the new spec. I agree that it needs to be put back.

/ Jonas
Received on Tuesday, 18 February 2014 17:21:54 UTC

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