[whatwg] Specification of window.find()
waldron.rick at gmail.com
Wed Feb 15 11:57:29 PST 2012
+1 to TJ's mention of find for use in the Selector API:
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
> > 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.
More information about the whatwg