Sean Hogan wrote:
Lachlan Hunt wrote:
Sean Hogan wrote:
Gregory Reimer (the author of reglib) points out that
Element.matchesSelector would be useful for event delegation.
See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector
It would also neatly tie in with NodeFilter in
== Section 6. The NodeSelector Interface
The caller must pass a valid group of selectors.
That's an authoring requirement, explain how that is applicable?
The group of selectors must not use namespace prefixes that need to be
resolved.
That also sounds like an authoring requirement.
Doug Schepers wrote:
As a high-level comment, the SVG WG would prefer to see support for
namespaces in the specification. We believe that there will be an
increasing amount of (X)HTML+SVG content produced, and that there are a
number of cases where it would be easier for authors to have this
On Dec 8, 2008, at 17:26 , Lachlan Hunt wrote:
Since NSResolver was taken out, please consider adding hardcoded
namespace
prefixes for svg and xhtml similar to how the empty and any
namespaces are
handled by this draft.
Similar functionality was previously requested and rejected for the
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt [EMAIL PROTECTED] wrote:
== Section 6. The NodeSelector Interface
The caller must pass a valid group of selectors.
That's an authoring requirement, explain how that is applicable?
It seems perfectly applicable for the spec to define how the
Doug Schepers wrote:
Hi, Lachlan-
Lachlan Hunt wrote (on 12/8/08 11:26 AM):
Selectors are evaluated against a given element in the context the
entire DOM tree in which the element is located.
...in the context of?
I'm not sure how to phrase that any more clearly. It means that when
