Re: Change to Attr interface in light of XPath
Jonas Sicking <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CA+c2ei-zxOZi27Vz_pZt3k6V3m--cfsJgcg6-gk6BXeVj61YYQ@mail.gmail.com> |
On Tue, Mar 18, 2014 at 10:48 AM, Anne van Kesteren <[email protected]> wrote: > On Tue, Mar 18, 2014 at 5:33 PM, Anne van Kesteren <[email protected]> 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