You are completely right I missed Elements.getElementsBySelector. $$
is so attractive looking that I didn't look for related

Maybe should have a
reference to 'Elements.getElementsBySelector'.


On Mar 30, 9:13 pm, "Andrew Dupont" <[EMAIL PROTECTED]> wrote:
> Element#getElementsBySelector lets you specify a context node other
> than the document. (
> getElementsBySelector)
> I can only speak for myself, but the reason I haven't felt the need to
> add any documentation on the Selector class itself is because I can't
> think of a case where someone would need to use Selector in a way that
> isn't afforded by $$ and Element#getElementsBySelector.  But if anyone
> can think of such a case then I'm all ears.
> Cheers,
> Andrew
> On Mar 30, 8:02 pm, "Jacob  Rockowitz" <[EMAIL PROTECTED]> wrote:> The $$ 
> function is great. I am assuming the Selector.findChildElements
> > method can be faster then $$ when you specify the exact starting
> > element for a search instead of $$ which searches the whole document.
> > Please correct me if I am wrong.
> > Anyway, should the Selector object be included in the documentation?
> > I figured I would post this since I hesitated using '
> > Selector.findChildElements' since it is not in the current docs.
> > thanks,
> > ~jake

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to