W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2012

[whatwg] Specification of window.find()

From: Rick Waldron <waldron.rick@gmail.com>
Date: Wed, 15 Feb 2012 14:57:29 -0500
Message-ID: <CAHfnhfr9LYQ1pU_=QqmU+w2A8+a6xLAAris9UmxSr9Ky0CS4Fg@mail.gmail.com>
+1 to TJ's mention of find for use in the Selector API:

http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0277.html


Rick



On Wed, Feb 15, 2012 at 2:49 PM, Tab Atkins Jr. <jackalmage at gmail.com>wrote:

> On Wed, Feb 15, 2012 at 11:26 AM, Ian Hickson <ian at hixie.ch> wrote:
> > So I guess we have to make a decision for the platform here.
> >
> > Do we want:
> >
> >  - To spec window.find() in all its historical glory, and have it
> >   implemented everywhere?
> >
> >  - To spec a subset of window.find() that just does the use case
> described
> >   above, namely to destructively change the selection to a matching part
> >   of the DOM so that it can be manipulated by script?
> >
> >  - To spec a new API that just returns matching ranges and then allows
> >   those ranges to be manipulated like the selection can be today?
> >
> >  - To encourage authors to write a library that does this for them, and
> >   not bother to provide a dedicated API at all?
> >
> > Which would implementations that don't do the full window.find() today be
> > willing to do?
>
> As far as I know, we (google) would prefer to do nothing with
> window.find(), so we can use it for the Selectors API.  No opinion on
> whether the functionality is useful under another name.
>
> ~TJ
>
Received on Wednesday, 15 February 2012 11:57:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:11 UTC