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 <o...@chromium.org<javascript:;>> > wrote: > > On Tue, Oct 25, 2011 at 4:44 PM, Bjoern Hoehrmann > > <derhoe...@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