Closed
Bug 1168203
Opened 10 years ago
Closed 10 years ago
interpolation of d attribute in SVG <animate> fails (simple test case)
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: david.dailey, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; HPDTDF; BRI/1; InfoPath.2; .NET4.0C; BRI/2; .NET4.0E; BOIE9;ENUSMSNIP; rv:11.0) like Gecko
Steps to reproduce:
http://cs.sru.edu/~ddailey/bugs/goose0.svg
Actual results:
Example on left does not animate. example on right (transformed) does.
Both animate in Chrome/Win
Expected results:
I can't see what about the values of d should cause the trouble.
I simplified the test case here down from http://cs.sru.edu/~ddailey/ello/goose2.svg in which many parts of the animation are not working in FF.
Comment 1•10 years ago
|
||
It's not legal SMIL to start durations with a . they must start with a number so 0.6 is valid and .6 is not. Chrome gets this wrong so either raise a Chrome bug or a SVG/SMIL specification bug.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Comment 2•10 years ago
|
||
The actual syntax is defined here: http://www.w3.org/TR/2001/REC-smil-animation-20010904/#Timing-ClockValueSyntax and Firefox follows the specification exactly as written.
| Reporter | ||
Comment 3•10 years ago
|
||
Thanks, Robert! I'll try to remember. It is hard since in the early days of SVG, .6 was allowed nowhere (gradients, durations, starttimes, proportions etc.), but over time, it has generally spread into acceptable in more contexts. I think raising a but with Chrome might be worthwhile since if they were proactive they'd raise a bug with SVG WG, perhaps, but apparently, they have abandoned web standards, at least vis a vis SVG? The example at http://cs.sru.edu/~ddailey/ello/goose2.svg has been fixed and is now working properly.
Comment 4•10 years ago
|
||
.6 is allowed in anything that is not SMIL so it would work in gradients.
You need to log in
before you can comment on or make changes to this bug.
Description
•