On Sep 30, 2006, at 04:21, Daniel Glazman wrote:
Robin Berjon wrote:
I don't think we need to cram as many features as possible into
v1. Defining the exact semantics of scoped CSS selectors can be a
little tricky, and it clearly is the job of the CSS WG to do so.
The WG thinks
Tricky. Ah
On Sat, 30 Sep 2006 04:21:39 +0200, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
The one and only issue is the :root matching, and it makes perfect
sense here to say it matches the root of the subtree because there
is no other root element in this context ! The other option, ie match
the root of
Robin Berjon wrote:
I don't think we need to cram as many features as possible into v1.
Defining the exact semantics of scoped CSS selectors can be a little
tricky, and it clearly is the job of the CSS WG to do so. The WG thinks
Tricky. Ah. When it comes to defining how matchSingle() and mat
Hi Daniel,
just expanding on some of Anne's arguments.
On Sep 29, 2006, at 09:50, Daniel Glazman wrote:
1. I think the title of the document is badly chosen.
The WG went through that discussion already. Unless new arguments can
be provided than those which have already been beaten to death
On Fri, 29 Sep 2006 10:54:36 +0200, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
Well having matchSingle and matchAll reply two different things is from
here hardly acceptable too... That means that a given code will have to
implement two different handlers depending on the queried set, first one
Anne van Kesteren wrote:
5. Disruptive Innovations SARL becoming a W3C member on the 1st of
October, we are ready to help on this specification.
If you could provide a testsuite, that'd be cool!
We'll do better : we'll provide a JS cross-browser implementation for
all CSS 3 selectors (e
Anne van Kesteren wrote:
4. I really hate having two different methods for matchSingle and
matchAll, and I'd prefer a single method with a boolean indicating
if only the first result should be retrieved or all. The result
should always be a StaticNodeList. If the boolean is true, th
On Fri, 29 Sep 2006 09:50:45 +0200, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
1. I think the title of the document is badly chosen. The spec*
does not offer any API on selectors themselves but, in substance,
offers an implementation for document.getElementsBySelector().
Since we ma