Open
Bug 648529
Opened 15 years ago
Updated 2 years ago
SVG elements in defs typically not identified as animation targets
Categories
(Core :: SVG, defect)
Tracking
()
NEW
People
(Reporter: dr.o.hoffmann, Unassigned)
References
(Depends on 1 open bug, )
Details
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0
If elements from within a defs element are referenced with use, the animation
is typically ignored, if the animation element is not a direct child of the
animated element with implied identification of the target element.
If the element is identified otherwise as animation target, the animation is
ignored.
About the example/test case:
The radii of circles in a defs-area are animated and then
referred with use. Several positions for the animation element
in the source code are tested.
A red comparison is available without use. This has to be covered always completely.
If something red gets visible, an error is occured.
Reproducible: Always
Steps to Reproduce:
1. Try the sample given above
2. Compare with description and specification (of use, cloning etc)
3. Compare with the behaviour of other viewers, for example Opera or the adobe plugin
Actual Results:
Only the blue circle top left is animated, this has the animate element
directly inside the circle element without using XLink:href.
For the other circles other variants are used to identify them as animation
target, respectively one set is used with an animation of XLink:href to reference an animated circle. For all these variants, the animation is ignored, respecitively the animation target not found.
Expected Results:
Animated blue circles should always cover the red comparison. This indicates,
that all circles (and one use element) have been identified as animation targets,
whatever method is used.
Comment 1•15 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:5.0a2) Gecko/20110417 Firefox/5.0a2
Marking issue as New.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•