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

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

From: Ojan Vafai <ojan@chromium.org>
Date: Tue, 25 Oct 2011 18:59:49 -0700
Message-ID: <CANMdWTv5xF4zSz6X_tYY7kZeMzJeb3x5dmrbaurFhA48VSmuJA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, public-webapps@w3.org
On Tue, Oct 25, 2011 at 4:58 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Tue, Oct 25, 2011 at 4:56 PM, Ojan Vafai <ojan@chromium.org> wrote:
> > On Tue, Oct 25, 2011 at 4:44 PM, Bjoern Hoehrmann <derhoermi@gmx.net>
> 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.


With my web developer hat on, I would expect the selector list version to
just be a comma-separated list of any valid single selectors. We should
either allow it in both cases or neither IMO. My preference is to allow it.

Ojan
Received on Wednesday, 26 October 2011 02:00:42 GMT

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