Re: [css3-transforms] Testing as stand-alone SVGs.

----- Mail original -----
De: "Peter Linss" <>
À: "Tavmjong Bah" <>
Envoyé: Mercredi 13 Juin 2012 20:09:35
Objet: Re: [css3-transforms] Testing as stand-alone SVGs.

On May 10, 2012, at 8:09 AM, Tavmjong Bah wrote:

> Hi,
>  I see that a lot of work has gone into creating CSS3 Transforms tests
> which include SVG embedded in either HTML or XHTML.[1] What is missing
> is the ability to test standalone SVG. I have written a short script
> which converts the HTML/XHTML based test into standalone SVG tests using
> the template that the SVG group has approved.[2] I've uploaded an
> example of a converted file to the SVG WG Mercurial site.[3]

The test suite build code already handles format conversion between XHTML and HTML, I was planning on adding support for HTML to SVG as well. I think it would be best for this to be handled as part of the build where practical.

Tav, can you send me the code you used for the conversion? I'm working on the build code next week and would be happy to integrate it.

TAV: Done. Code was written specifically for Adobe's CSS3 transform tests and may not work generically.

>  How can these files be included in the test framework that is accessed
> from the Editor's draft? Two things would be desirable:

Just getting the tests in the repository at with the proper metadata present should be sufficient.

One of the features I'll be adding to the build code is to allow multiple source formats for the same test where needed (it already produces multiple output formats).

> 1. To be able to tag a browser as passing/failing for a stand-alone SVG
> in the same way that is done with the HTML/XHTML versions.

This raises an interesting question. Currently when an implementation passes a test in any format available, it's considered passing (even if it fails in another format).

Do we need to track pass/fails for stand-alone SVG tests separately from the same test as SVG in HTML?

TAV: Yes, I think. Otherwise problems with stand-alone SVG will be overlooked. At the moment, I think none(?) of the major browsers handle CSS3 transforms in stand-alone SVG but then do with SVG embedded in HTML.

> 2. The ability to include results from non-browsers. This is important
> for SVG. Four out of the eight SVG renderers used for the SVG 1.1 second
> edition Implementation Report are not web browsers.[4]
>  It appears that the SVG specific tests don't actually test the use of
> CSS but include the transforms as presentation attributes. Is there a
> plan to include testing as CSS styling properties?
>       Tav
> [1]
> [2]
> [3]
> [4]

Received on Wednesday, 13 June 2012 20:28:44 UTC