W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

Re: Problem with test udom-dom-203-t.svg

From: Erik Dahlström <ed@opera.com>
Date: Wed, 12 Nov 2008 17:20:43 +0100
To: "Chris Lilley" <chris@w3.org>, "Cyril Concolato" <cyril.concolato@enst.fr>
Cc: cyril.concolato@telecom-paristech.fr, public-svg-wg@w3.org
Message-ID: <op.ukik0tsegqiacl@gnorps.linkoping.osa>

On Wed, 12 Nov 2008 14:45:53 +0100, Chris Lilley <chris@w3.org> wrote:

> On Wednesday, November 5, 2008, 11:24:54 AM, Cyril wrote:
> CC> Hi Erik,
> CC> Erik Dahlstrom a écrit :
>>> Cyril wrote:
>>>> The test udom-dom-203-t.svg uses access to textContent and performs
>>>> some string comparisonto decide if the test is a pass or fail. But
>>>> this assumes that text normalization is done.This is optional in the
>>>> spec so the test should be modified.
>>> What revision of the test? I recall fixing this test recently [1],
>>> revision 1.8 should be fine.
> CC> Indeed, we were using the version in svggen (version 1.7) instead
> CC> of the version in svg (version 1.8).
> CC> With version 1.8, it passes.
> IIRC we agreed that there was no good reason to make an svggen anymore - the implementations can all deal with the multiamespace fikes in /svg/ which are more current. There is version mismatch a downside to using /svggen/.
> I forget if someone had an action to fix the script that makes the harness?

I started looking at the scripts at the TPAC I think, and it seems relatively easy to modify them. There's no action assigned for it AFAIK.


Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Wednesday, 12 November 2008 16:21:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:09 UTC