W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

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

From: Yehuda Katz <wycats@gmail.com>
Date: Tue, 25 Oct 2011 17:03:29 -0700
Message-ID: <CAMFeDTUmORotLMyRqp4pgCKe8cbM7FPszhfroHsrpU=2QZ5+ew@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Ojan Vafai <ojan@chromium.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, "public-webapps@w3.org" <public-webapps@w3.org>
fwiw, jQuery doesn't properly handle the comma-separated case, but this is
most definitely a bug, caused by the na´ve implementation that Alex showed
early on in this thread.

-- Yehuda

On Tuesday, October 25, 2011, Tab Atkins Jr. wrote:

> On Tue, Oct 25, 2011 at 4:56 PM, Ojan Vafai <ojan@chromium.org<javascript:;>>
> wrote:
> > On Tue, Oct 25, 2011 at 4:44 PM, Bjoern Hoehrmann <derhoermi@gmx.net<javascript:;>>
> wrote:
> >>
> >> * Tab Atkins Jr. wrote:
> >> >Did you not understand my example?  el.find("+ foo, + bar") feels
> >> >really weird and I don't like it.  I'm okay with a single selector
> >> >starting with a combinator, like el.find("+ foo"), but not a selector
> >> >list.
> >>
> >> Allowing "+ foo" but not "+ foo, + bar" would be "really weird".
> >
> > Tab, what specifically is weird about el.find("+ foo, + bar")?
>
> Seeing a combinator immediately after a comma just seems weird to me.
> This may just be a personal prejudice.
>
> ~TJ
>
>

-- 
Yehuda Katz
(ph) 718.877.1325
Received on Wednesday, 26 October 2011 00:03:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT