While what is being talked about here is confusing me, there are valid
uses for a method of restricting a .find based on a selector. That's a
feature I'd like to see.
$(NavFrame).find('.NavContent, .NavPic' /* some way of restricting to
outside nested .NavFrames */);
That being said, I don't like the context idea, to me a second
‘restrict’ argument makes the most sense. "keep options relevant to X
method in X method's arguments"
~Daniel Friesen (DanTMan, Nadir Seen Fire) [http://daniel.friesen.name]
On 23-Jul-09, at 8:08 AM, John Resig <jere...@gmail.com> wrote:
>
> A big distinction between the two proposals is if DOMElement is not
> contained in DOMElementContext:
>
> $(DOMEelement,DOMElementContext).closest("body"); returns $([]);
>
> $(DOMEelement).closest("body",DOMElementContext); returns $("body");
>
> I vote for the 2nd argument.
>
> In what case would you want to find the closest() match but outside
> of a context? What's the point of providing a context then if most
> closest() queries will just ignore the context away?
>
> --John
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
