There's a ticket for this. We'll handle it, probably for 1.3. -- Ariel Flesler http://flesler.blogspot.com
On Oct 2, 5:20 pm, Matt Kruse <[EMAIL PROTECTED]> wrote: > On Oct 2, 11:42 am, Dave Methvin <[EMAIL PROTECTED]> wrote: > > >http://docs.jquery.com/Traversing/is#expr > > "If no element fits, or the expression is not valid, then the response > > will be 'false'. Note: Only simple expressions are supported. Complex > > expressions, such as those containing hierarchy selectors (such as +, > > ~, and >) will always return 'true'. > > Is there a reason, internally, why it would always return true instead > of false? It would seem to make much more sense to return false for > complex selectors. > > Or, preferably, if it's a complex selector evaluate it globally, then > check to see if the item to be matched is contained within the > results. This would be slow in some cases, for sure, but would > probably behave as many people expect. It seems like the behavior > of .is() confuses a lot of people when they first use it (myself > included). > > Matt Kruse
