- From: Cameron McCormack <cam@mcc.id.au>
- Date: Thu, 3 Jul 2008 17:41:58 +1000
- To: public-svg-wg@w3.org
Hi WG.
For ACTION-2074 I am to test how implementations handle empty string
values in animation values="" attributes, and whether the semicolon at
the end of that list is allowed or has any affect.
Opera 9.5:
▪ Doesn’t allow empty strings in values="".
▪ Allows a semicolon at the end of the values="" list and doesn’t
treat the (possibly zero-length) string after it as a value.
▪ Allows an empty string in to="".
Firefox 3:
▪ No animation support.
Batik 1.8pre:
▪ Doesn’t allow empty strings in values="" or to="" (there’s a parsing
bug in there where the semicolon after the empty string up to just
before the next semicolon is considered to be the next value).
▪ Allows a semicolon at the end of the values="" list and doesn’t
treat the (possibly zero-length) string after it as a value.
WebKit nightly:
▪ Does allow an empty string value in the middle of values="", but if
there is a trailing semicolon then the final value just before the
semicolon (and the empty string value after it) is ignored.
▪ An empty string value in to="" is supported.
ASV3 and Renesis I don’t have available to test right now. The file I
used for testing is:
http://dev.w3.org/SVG/profiles/1.1F2/ua-tests/animate-values-semicolon.svg
The updating numbers don’t mean anything (they just show the test is
running really). You just need to watch out for the animated xlink:href
values that are shown as the test progresses, and match them up with
what’s in the values="" in the source, to see how the implementation
handles the empty strings and semicolons.
--
Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 3 July 2008 07:42:57 UTC