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 Mar 2014 13:35:44 -0700
Message-ID: <CA+c2ei-zxOZi27Vz_pZt3k6V3m--cfsJgcg6-gk6BXeVj61YYQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, DOM public list <www-dom@w3.org>
On Tue, Mar 18, 2014 at 10:48 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Tue, Mar 18, 2014 at 5:33 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> It returns undefined in all implementations. (I didn't test this and
>> just went by your word initially, reverting that now.)
>
> It does work in Safari, but not Firefox or Chrome:
> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2892 And
> there is no other member that has such a pointer.

This seems to indicate that both Firefox and Chrome supports
ownerElement in actual released builds.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25086#c8

So do we have any data actually indicating that the web does *not*
depend on this property?

Seems silly to remove this given that it creates a less elegant API,
and that it doesn't really reduce implementation burden (you still
have to have a reference back to the element from the Attr object).

/ Jonas
Received on Tuesday, 18 March 2014 20:36:50 UTC

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