W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2012

Re: ACTION-3243: Mirror css test metadata setup in SVG and come up with a template for new tests (SVG Working Group)

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 08 Mar 2012 16:19:33 +1100
Message-ID: <4F584165.3070203@mcc.id.au>
To: Tavmjong Bah <tavmjong@free.fr>
CC: SVG Working Group <public-svg-wg@w3.org>
Tavmjong Bah:
> Done, see bottom of:
> http://www.w3.org/Graphics/SVG/WG/wiki/SVG2/Testing_Requirements

Thanks.

I would actually prefer to take this opportunity to simplify our 
template if we can.  I agree we should get rid of the CVS revision (as 
you mention, especially given that this won't work now that we're living 
in a Mercurial repository) and the frame around the test.

At Mozilla, we write our tests with a CC0 / public domain disclaimer at 
the top.  Is that something we could consider doing for our new test suite?

Regarding pulling out the CSS to show in the test harness page, although 
that is probably good for CSS tests I don't know how useful it would be 
for us.  Sure some tests might have their important behaviour in a style 
sheet, but not many.

I agree with dropping the red "DRAFT" banner for the reason you give.


For the format overall, my preference would be to have a simple format 
and have the CSS Testing Framework adapt to it.

I think if we can we should also choose a format that will parse 
elements into the same namespace in text/html, so that we don't have to 
have different document structure for SVG-in-HTML tests.  That means if 
we want to use HTML <link> and <meta> elements (which we don't need to 
if we don't want, really) we'd need to use <foreignObject>.

<svg xmlns="http://www.w3.org/2000/svg"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      viewBox="0 0 480 360">

   <title>DESCRIPTION OF TEST</title>

   <metadata>
     <foreignObject>
       <link xmlns="http://www.w3.org/1999/html" .../>
       <meta xmlns="http://www.w3.org/1999/html" .../>
     </foreignObject>
   </metadata>

   CONTENTS OF TEST
</svg>


We can't put <link> and <meta> in a <head>, because it's not allowed to 
have multiple <html> or <head> elements in the one document.  (And it 
won't turn up in the DOM.)


So it might be better to avoid using the HTML elements in our tests. 
Unfortunately we don't have analogues for <link> and <meta> in SVG at 
the moment.  I'd love it if we could just write:

<svg xmlns="http://www.w3.org/2000/svg"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      viewBox="0 0 480 360">

   <title>DESCRIPTION OF TEST</title>
   <link .../>
   <link .../>
   <meta .../>

   CONTENTS OF TEST
</svg>


Unfortunately (again) <meta> is one of the tags that breaks out of SVG 
parsing in text/html.

If we did introduce SVG <link> elements (not sure if we've 
discussed/agreed yet) then we could use those like the CSS test <link> 
elements.  I think the <meta name="assertion"> would fit well in <desc>. 
  We could use a data- attribute for the remaining <meta name="flags">.

<svg xmlns="http://www.w3.org/2000/svg"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      viewBox="0 0 480 360"
      data-flags="...">

   <title>DESCRIPTION OF TEST</title>
   <desc>TEST ASSERTION</desc>
   <link rel="author" title="..." href="..."/>
   <link .../>

   CONTENTS OF TEST
</svg>


I think that looks reasonable simple and easy to deal with.  WDYT?
Received on Thursday, 8 March 2012 05:20:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 8 March 2012 05:20:19 GMT