On Jan 27, 2009, at 00:18, Alex Russell wrote:
We just need to invent a pseudo-property for elements which can be
matched by a :not([someProperty=your_ns_here]).
To select SVG elements while avoiding HTML elements of the same name,
a selector that prohibits the local name foreignObject
On Wed, 28 Jan 2009 10:55:49 +0100, Henri Sivonen hsivo...@iki.fi wrote:
On Jan 27, 2009, at 00:18, Alex Russell wrote:
We just need to invent a pseudo-property for elements which can be
matched by a :not([someProperty=your_ns_here]).
To select SVG elements while avoiding HTML elements of
Maybe it was already proposed, but are there any problem to just add a
new argument to querySelectors and querySelectorsAll, with namespace
bindings?
I don't mean anything like XPathNSResolver or things like that. I just
mean a ES Object, where enumerable property names are namespace
prefixes,
I asked that question a little ago. I was answered, and agreed, that
CSS selectors are easier to understand, are already known by authors
because of their use in CSS and most important they're highly
optimized in UAs.
2009/1/28 Anne van Kesteren ann...@opera.com:
On Wed, 28 Jan 2009 14:25:29
On Wed, 28 Jan 2009 14:32:05 +0100, Giovanni Campagna
scampa.giova...@gmail.com wrote:
I asked that question a little ago. I was answered, and agreed, that
CSS selectors are easier to understand, are already known by authors
because of their use in CSS and most important they're highly
Giovanni Campagna wrote:
Maybe it was already proposed, but are there any problem to just add a
new argument to querySelectors and querySelectorsAll, with namespace
bindings?
The original spec did contain an NSResolover argument, which was based
upon the XPathNSResolver. It was dropped for
@Anne:
well, assuming that an author will need to match elements across
multiple namespaces, it will be easier to use XPath (that also is
compatible across multiple browsers) than to use horrible workarounds
like svg :not(foreignObject) *[href] (all svg links) or svg
not(timesheet) animation (all
a) authors create multiply namespaced documents, so they need a way to
reliably traverse those documents (either with namespace support or
not)
b) svg links support attributes that xhtml links (i mean xhtml2 links,
ie any element with a href) do not: modifying those attributes is a
use case (for
Giovanni Campagna wrote:
well, assuming that an author will need to match elements across
multiple namespaces, it will be easier to use XPath (that also is
compatible across multiple browsers) than to use horrible workarounds
like svg :not(foreignObject) *[href] (all svg links) or svg
2009/1/28 Boris Zbarsky bzbar...@mit.edu:
Giovanni Campagna wrote:
well, assuming that an author will need to match elements across
multiple namespaces, it will be easier to use XPath (that also is
compatible across multiple browsers) than to use horrible workarounds
like svg
Giovanni Campagna wrote:
2009/1/28 Boris Zbarsky bzbar...@mit.edu:
Giovanni Campagna wrote:
well, assuming that an author will need to match elements across
multiple namespaces, it will be easier to use XPath (that also is
compatible across multiple browsers) than to use horrible workarounds
2009/1/28 Boris Zbarsky bzbar...@mit.edu:
Giovanni Campagna wrote:
2009/1/28 Boris Zbarsky bzbar...@mit.edu:
Giovanni Campagna wrote:
well, assuming that an author will need to match elements across
multiple namespaces, it will be easier to use XPath (that also is
compatible across
Giovanni Campagna wrote:
2009/1/28 Boris Zbarsky bzbar...@mit.edu:
svg xmlns=http://www.w3.org/2000/svg;
g
foreignObject
foo xmlns= href=This is my random href attribute/
/foreignObject
/g
/svg
The foo element matches the svg :not(foreignObject) *[href] selector.
On Mon, 26 Jan 2009 18:21:21 +0100, Lachlan Hunt lachlan.h...@lachy.id.au
wrote:
Lachlan Hunt wrote:
Erik Dahlström wrote:
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt
lachlan.h...@lachy.id.au wrote:
== 8. Examples
Please add an example such as this one:
...
Then explain how to
Hi Alex,
On Jan 27, 2009, at 18:13 , Alex Russell wrote:
I really do loathe namespaces, but is the selectors API actually
going to be this impoverished?
I understand your argument, but I'm afraid you're beating a dead
horse. This ship has pretty much sailed, and agreement has been
Alex Russell wrote:
So to recap:
1.) someone made a mistake by allowing namespaces in XML
2.) SVG makes heavy use of this feature as a way to specify many
intrinsic operations for which HTML simply adds local tags (e.g., links)
3.) well intentioned attempts to unify the platform
Lachlan Hunt wrote:
Erik Dahlström wrote:
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt
lachlan.h...@lachy.id.au wrote:
== 8. Examples
Please add an example such as this one:
...
Then explain how to use the Selectors API to select only the svg
'font' elements and how to select only the
Alex Russell wrote:
Can this be represented in a :not() clause somehow? Foisting more work
onto script is the wrong answer.
No. The SVG WG explicitly requested an example illustrating how to
filter elements based on the namespace URI that works in the general
case, given that there is no
On Jan 26, 2009, at 1:49 PM, Lachlan Hunt wrote:
Alex Russell wrote:
Can this be represented in a :not() clause somehow? Foisting more
work onto script is the wrong answer.
No.
How about not yet?
Needing to do this filtering in script is clearly a spec bug. QSA is
already littered
Hi, Alex-
Alex Russell wrote (on 1/26/09 5:18 PM):
Don't get me wrong, I'm no lover of namespaces. Frankly I think
they're a bug. But SVG is stuck w/ 'em until it can find a
way to evolve out of the XML ooze.
LOL - evolve out of the XML ooze
Until that time, we must surely be able to
Alex Russell wrote:
On Jan 26, 2009, at 1:49 PM, Lachlan Hunt wrote:
Alex Russell wrote:
Can this be represented in a :not() clause somehow? Foisting more
work onto script is the wrong answer.
No.
How about not yet?
I think the more correct answer is not in this version.
/ Jonas
On Dec 9, 2008, at 01:06 , Lachlan Hunt wrote:
Robin Berjon wrote:
On Dec 8, 2008, at 17:26 , Lachlan Hunt wrote:
Similar functionality was previously requested and rejected for
the xml and xmlns prefixes, and I see no reason to treat the xhtml
and svg prefixes any differently.
On Mon, 08 Dec 2008 20:12:11 +0100, Erik Dahlström [EMAIL PROTECTED] wrote:
IMHO the spec is trying to require something that is not enforcable
anyway, and might as well not mention it, but instead just describe what
happens for all possible indata.
Valid SVG, valid XHTML, or valid HTML
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt [EMAIL PROTECTED] wrote:
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
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
On Dec 9, 2008, at 10:28 , Anne van Kesteren wrote:
On Mon, 08 Dec 2008 20:12:11 +0100, Erik Dahlström [EMAIL PROTECTED]
wrote:
IMHO the spec is trying to require something that is not enforcable
anyway, and might as well not mention it, but instead just describe
what happens for all
On Dec 9, 2008, at 12:46 , Erik Dahlström wrote:
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt [EMAIL PROTECTED]
wrote:
As a compromise, we believe that if the NSResolver support remains
removed from this specification, there should be explicit mention of
workarounds (see below), and an
== 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:
Please add an example such as this one:
html xmlns=http://www.w3.org/1999/xhtml;
body
svg xmlns=http://www.w3.org/2000/svg;
font id=mysvgfont
...
/font
/svg
font face=ArialExample/font
svg:font id=anothersvgfont
32 matches
Mail list logo
