You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by Christophe Jolif <cj...@ilog.fr> on 2000/12/01 08:50:05 UTC
createElement/createElementNS problem
It seems that Jon & Chris (the only ones to have expressed opinions on
that in the WG) consider that in the case of an SVGDocument (not a
generic Document) createElement should return SVGElement and not generic
Element. If I well understand this will mean we will have to modify our
SVG DOM implementation to follow this if we want to be compatible...
-------- Original Message --------
Subject:
Re: dom-EventListeners-BE-04.svg
Resent-Date:
Thu, 30 Nov 2000 15:36:11 -0500 (EST)
Resent-From:
w3c-svg-wg@w3.org
Date:
Thu, 30 Nov 2000 21:34:57 +0100
From:
Chris Lilley <ch...@w3.org>
Organization:
W3C
To:
Christophe Jolif <cj...@ilog.fr>
CC:
Jon Ferraiolo <jf...@adobe.com>, SVG Working Group
<w3...@w3.org>
References:
1 , 2 , 3
Christophe Jolif wrote (well, quoted the spec):
> To create an element with a qualified name and namespace URI, use
> the createElementNS
Yes, but if there is namespace defaulting then you can use unqualified
names and they are still in a particular namespace.
In other words, as long as you don't need to create foo:rect or
whatever,
then you are OK.
-------- Original Message --------
Subject: Re: dom-EventListeners-BE-04.svg
Resent-Date: Thu, 30 Nov 2000 12:45:44 -0500 (EST)
Resent-From: w3c-svg-wg@w3.org
Date: Thu, 30 Nov 2000 09:44:43 -0800
From: "Jon Ferraiolo" <jf...@adobe.com>
To: Chris Lilley <ch...@w3.org>
CC: Christophe Jolif <cj...@ilog.fr>, SVG Working Group
<w3...@w3.org>
References: <3A...@ilog.fr>
At 11:47 PM 11/29/00 +0100, Chris Lilley wrote:
[...]
I don't agree. The createElement() method will create an element in the
same namespace as the document, which in this case is SVG, isn't it? I
don't see why we need to createElementNS(). If this were true, then
every
HTML script which calls createElement() would also be incorrect.
Jon
>--
>Chris