Re: Change to Attr interface in light of XPath

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.

-Boris

Received on Tuesday, 18 February 2014 17:15:35 UTC