Selector queries return wrong nodes about base2 HOT 9 CLOSED

It looks that selector queries are broken and unusable in current version.. only
simpliest queries return expected values.

> only simpliest queries return expected values.

Can you provide some more examples? I've fixed the submitted issue before I 
check it
in I'd like to know I've fixed the other issues.

What I see is that all queries that:
- consist of more than one simple sequence
- should return elements within given scope and not document scope
return elements within document scope.
And that's all issues that I see at the moment.

What do you mean by "consist of more than one simple sequence"? Can you provide 
an
example? I'd like to close this bug otherwise as I've fixed the scoping issue in
Firefox/Opera.

By simple selector sequence I understand e.g. 'div[attr="value"]' by two simple
selector sequences I understand e.g. 'div[attr="value"] div[attr="value"]'

So - el.matchSingle("div") returned right element but el.matchSingle("div div") 
not

I took this naming from Selectors W3C recommendation and quite old proposal to 
CSSOM
by Daniel Glazman - probably I should revise my naming convention ;-)

I saw that you've started updating library builds (base and DOM are available 
while
BOM returns 404 at the moment) - after I've updated base and DOM files, 
selectors
like "div div" works ok but now I have problem with multiple selector - check
http://mariuszn3.com/base2/selectors.html matchAll returns two elements while 
should
return just one (input is outside of scope but it's returned)

Bah! I still haven't fixed the scoping issue for comma separated selectors. 
I'll do
that now.

PS. The BOM package has been removed.

OK. I think I've fixed the scoping issues for real now. I'm marking this bug 
fixed.
Can you verify?

It works great - I don't see any issues right now.
I let you know if I'll find any other problem. Thanks!