Tests required for recent changes to SVG 1.1 Second Edition

Hello WG.

I went through the list of changes for the errata that were already
folded in, and the other small changes that have been made that aren’t
captured in errata, and came up with a list of tests that we should
make:

  * Test that presentation attributes on elements that previously
    disallowed them are recognised.  (Such as by using
    getPresentationAttribute and getComputedStyle.)

  * Test kernelUnitLength on feSpecularLighting (since it is now
    defined).  However there aren’t any tests at all for
    kernelUnitLength on either of the lighting filter primitives (or on
    feConvolveMatrix)!

  * Test that style/class attributes on filter primitives that
    previously didn’t allow them now have an effect, e.g. by
    using SVGStylable::{style,className}, getComputedStyle and
    changes to filter behaviour.

  * Test that SVGFESpecularLightingElement::kernelUnitLength[XY] reflect
    the correct values, and that changing them has an effect.

  * Test animating @xlink:href on feImage.

  * Test feComponentTransfer when transfer function elements are omitted
    or repeated.  (There might actually be a test for this one already.)

  * Test that SVGFEConvolveMatrixElement::in1 works.

  * Test that @azimuth on feDistantLight is interpreted as clockwise.

  * Test that @seed on feTurbulence is truncated towards zero.

  * Test that color-interpolation-filters doesn’t cause a colour space
    conversion on ‘in’ for feDisplacementMap.

  * Test that default value for contentScriptType is
    application/ecmascript.  (Though I’m not sure what this would
    actually test; default encoding of external scripts?  Do browsers
    really want to do this rather than sniffing?)

Some of the above I can’t do, since I’m not enough of a filter/colour
guru.

Thanks,

Cameron
ACTION-2573

-- 
Cameron McCormack ≝ http://mcc.id.au/

Received on Thursday, 28 May 2009 07:17:08 UTC