W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments

From: Scott González <scott.gonzalez@gmail.com>
Date: Thu, 10 Oct 2013 16:26:33 -0400
Message-ID: <CAO8i3ifqSOkhfJETkk39TZuu3=Pdz4PX5AqZQhmgbdSXGuTMOA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: WHATWG <whatwg@lists.whatwg.org>, Zirak A <zirak@mail.com>
On Fri, Sep 6, 2013 at 8:47 AM, Scott González <scott.gonzalez@gmail.com>wrote:

> On Fri, Jun 28, 2013 at 6:51 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:
>
>> On Fri, Jun 28, 2013 at 2:28 PM, Zirak A <zirak@mail.com> wrote:
>>  > Besides my personal aversion towards selectors being in the DOM API,
>> there's
>> > also the simple fact that it makes sense for document fragments to have
>> these
>> > methods.
>>
>> That's far from obvious, given that I don't think it makes sense to
>> spread those obsolete methods around any further.
>>
>
> They were already spread to ShadowRoot. Does anyone have a reference to
> that discussion that led to that decision? It seems like if they're being
> added to ShadowRoot, which inherits from DocumentFragment, we might as well
> just add them to DocumentFragment and be done with it. At least from a
> non-implementor's view that seems to make sense.
>

I don't think there was any response to this. What is the reason for
keeping these methods off of DocumentFragment if new APIs which inherit
from DocumentFragment are going to have the methods anyway?
Received on Thursday, 10 October 2013 20:26:58 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC