W3C home > Mailing lists > Public > www-svg@w3.org > August 2002

RE: [SVG1.0] no tspan allowed inside an anchor?

From: Thomas E Deweese <thomas.deweese@kodak.com>
Date: Mon, 19 Aug 2002 10:34:40 -0400
Message-ID: <15713.512.840287.120131@frog.rl.kodak.com>
To: Jon Ferraiolo <jon@ferraiolo.com>
Cc: "'Jim Ley'" <jim@jibbering.com>, www-svg@w3.org

>>>>> "JF" == Jon Ferraiolo <jon@ferraiolo.com> writes:

JF> [...] In fact, I would argue that from an accessibility
JF> perspective, it is better to have separate elements. (Thus, your
JF> opinion is not shared by all.)

JF> But most importantly, the cat is out of the bag. [...]

JF> Overall, I don't believe that it is worth disrupting the SVG
JF> community by deprecating <tspan>.

Me2 :)

JF> However, I think the working group should reevaluate the
JF> restriction on <a> and <tspan>. Tobi (I think) pointed out that we
JF> might be able to do something the XML Schema or at least via
JF> supplemental notes in the spec to prevent this from being legal:

JF> <svg> <a> <tspan>

    It is possible to make this illegal in W3C Schema (elements can
have different content models in different contexts).  I also believe
that this is the correct solution to the problem.
Received on Monday, 19 August 2002 10:34:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:53:55 UTC