Re: [selectors-api] QSA and findAll definitions

2013-06-10 Thread Timmy Willison
to me that elem.find() will never return ancestors of elem. On Mon, Jun 10, 2013 at 10:53 AM, Tab Atkins Jr. jackalm...@gmail.comwrote: On Sun, Jun 9, 2013 at 6:18 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 6/9/13 7:35 PM, Timmy Willison wrote: I was a little confused. I realized something I

Re: [selectors-api] QSA and findAll definitions

2013-06-10 Thread Timmy Willison
On Mon, Jun 10, 2013 at 4:47 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: Just throw away your notion that .find() does any scoping whatsoever. Ok, will do. It doesn't; all it does is provide a reference element, which is matched by :scope and which is used to absolutize relative

[selectors-api] QSA and findAll definitions

2013-06-09 Thread Timmy
querySelector is supposed to do. Element#querySelector returns results based off of the tree in which the element is located. Thanks, - Timmy

Re: [selectors-api] QSA and findAll definitions

2013-06-09 Thread Timmy Willison
] and .querySelector[All] relate to the context object? Why the wording difference? Thanks again,  - Timmy On Sun, Jun 9, 2013 at 5:34 PM, Timmy timmywill...@gmail.com wrote: The wording of the QSA and findAll definitions are a bit confusing to me. Forgive me if I'm misunderstanding

Re: [XHR] remove user cancels request

2013-02-24 Thread Timmy Willison
is only fired as a result of a call to abort(). +1 -- Glenn Maynard - Timmy

Re: QSA, the problem with :scope, and naming

2011-10-22 Thread Timmy
equivalent to deprecating them, which would be a win. This is extraneous. The implementation of custom pseudo selectors would be identical. - Timmy