Animate does not animate related <use> elements
Categories
(Core :: SVG, defect)
Tracking
()
People
(Reporter: david, Assigned: longsonr)
References
(Blocks 9 open bugs)
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:11.0) Gecko/20100101 Firefox/11.0 Build ID: 20120310010446 Steps to reproduce: Created SVG with a path with a animateTransform child element linked to mouseover (black circle). Cloned that path several times (red, green and blue circles). Tried mouse over each element in turn (original path and use elements) Actual results: mouseover on use elements animates individually, as expected. However, mouseover on original path only animates that path and not use elements Expected results: Spec isn't clear on this but I anticipated that mouseover on original path would animate use elements since they mimic all properties of the original. This came from testing a bug in Webkit (https://bugs.webkit.org/show_bug.cgi?id=81792). With webkit mouseover on <use> calls all sibling <use> elements to animate, which is definately incorrect. I would like correct behaviour on triggering animation on a element which is cloned with <use> to be agreed and implemented the same across browsers. (please!)
Assignee | ||
Updated•12 years ago
|
Reporter | ||
Comment 2•12 years ago
|
||
Thank you, Robert. I did search but didn't come across this one. Is the compliant behaviour then that animating an object should animate all related <use> clones?
Assignee | ||
Comment 3•12 years ago
|
||
It is and that's what that bug is about.
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Comment 6•8 years ago
|
||
Hi all. Given that 1194728 is a duplicate, then it is highly likely, it would seem, that this is also: http://cs.sru.edu/~ddailey/ello/BasicPuebloSpiral.svg same symptoms -- reused stuff doesn't animate properly. See also instance at https://ello.co/ddailey/post/GwFlnDl399lyp_SVHhGM0A where embedded in social media.
Wait for 2 seconds for the fixed-time animations. Click on the red bars to trigger animations. Groups are animate animateTransform set animateMotion Each group has first line: animationElement.beginElement() second line: begin="trigger.click" third line: begin="2s" left column: animated element, right column: <use> Whether the <use> element is animated differs between the animation elements, and it differs between the way the animation is started: - <animate> and <set>: The <use> element is animated if the animation on its relative element is started at a fixed time or via a begin="otherElem.event" attribute, but not if it is started via the beginElement() method. - <animateTransform> and <animateMotion>: The <use> element is never animated.
I just found an even stranger behavior, see https://gist.github.com/ccprog/ae3e2fa676cf902a1e33622e695acbb8 A path with an animateTransform is referenced in a <use> element twice: once, for direct rendering, and once as part of a mask. The animation is triggered with a begin="trigger.mouseover". The direct reference does not show the animation, but the masked element (which means, twice removed) has it working.
Updated•1 year ago
|
Comment 11•1 year ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 4 duplicates.
:jwatt, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 12•1 year ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Comment 13•3 months ago
|
||
SVGObserverUtils will allow us to observe all changes to the corresponding elements.
We turn off SMIL animation on the cloned elements as we'll now update from the corresponding
elements instead. That will keep all the animations in sync and stop us from having the
animations cancel when the animation elements are deleted from the clones (as they are not
SVGGraphicsElements).
As we're now dependent on the corresponding elements for animation we need to make sure we
don't throttle their animations.
Assignee | ||
Comment 14•3 months ago
|
||
Also fixes bug 575470 as we determine the correct target and relatedTarget for
events that are sent to the elements the use elements have cloned.
The following historic w3c test works too:
As does
https://bug738574.bmoattachments.org/attachment.cgi?id=608634
Depends on D187262
Assignee | ||
Comment 15•3 months ago
|
||
Assignee | ||
Comment 16•3 months ago
|
||
Assignee | ||
Updated•2 months ago
|
Description
•