- From: Nikolas Zimmermann <zimmermann@physik.rwth-aachen.de>
- Date: Tue, 12 Oct 2010 09:06:06 +0200
- To: Shane Stephens <shans@google.com>
- Cc: www-svg@w3.org
Hi Shane, I think you are misunderstanding something: > <path d="M-25,-12.5 L25,-12.5 L 0,-87.5 z" fill="yellow" > stroke="red" stroke-width="7.06" id="MyTriangle" > > </path> > <animateMotion dur="6s" repeatCount="indefinite" rotate="auto" > > <mpath xlink:href="#path1"/> > </animateMotion> This example is not correct, how shall the user agent know to which element the animation should be applied? It works as expected if you'd assign xlink:href="#MyTriangle" to your <animateMotion> element. You either have to specify a target for your animation element using xlink:href=#someIRI" or include it as child element of the target element. I just played a bit around with your test in Opera, and it's confusing: If I try: <path d="M-25,-12.5 L25,-12.5 L 0,-87.5 z" fill="yellow", stroke="red" stroke-width="7.06" id="MyTriangle"/> <rect width="30" height="30"/> <animateMotion dur="6s" repeatCount="indefinite" rotate="auto" ><mpath xlink:href="#path1"/></animateMotion> Then Opera animates both the path & the rect, using the same animateMotion operation. Sounds like a bug to me, unless I'm missing some SMIL detail. Erik? > <path d="M-25,-12.5 L25,-12.5 L 0,-87.5 z" fill="yellow" > stroke="red" stroke-width="7.06" id="MyTriangle" > > <animateMotion dur="6s" repeatCount="indefinite" rotate="auto" > > <mpath xlink:href="#path1"/> > </animateMotion> > </path> Here, you are including the animateMotion element as <path> child, so it works fine. Cheers, Niko
Received on Tuesday, 12 October 2010 07:06:37 UTC