Issue 102998 in chromium: SVG animation flickering

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined

New issue 102998 by atodo...@packetscale.com: SVG animation flickering
http://code.google.com/p/chromium/issues/detail?id=102998

Chrome Version : 15.0.874.106 m
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: FAIL
Firefox 4.x:
IE 7/8/9:
Firefox 7.0.1: OK

What steps will reproduce the problem?
1. open HTML file in the attached zip
2. Jusst look the progress of the bar

What is the expected result?
Animated bar progress in 30 steps then start from beginning

What happens instead?
after few animations the bar becomes buggy:
- aninmate to next level but not freeze at it (the value of width is
= 'from' value instead of 'to' value)
- start animating from 1 step before current expected

Please provide any additional information below. Attach a screenshot if
possible.

It is working fine on Firefox 7.0.1 and Linux Chromium 14.0.835.202 on
Ubuntu 11.10 (developer build 103287)

It fail on Safari 5.1.1 (windows) so probably it is WebKit bug.

Looking the element width in developer tools it is clear that animation is
stoppped at 'from' field instead at 'to' field, sometimes the value of
width is x.xxxxxxx-xxxe instead of desired integer.

Similar misbehaviour is detected on animateColor element but it is hard to
create visible proof. (Probably writing javascript to check the actual with
expected value...)

Attachments:
svgAnimateTest.zip 627 bytes

[chro...@googlecode.com]

Comment #1 on issue 102998 by atodo...@packetscale.com: SVG animation
flickering
http://code.google.com/p/chromium/issues/detail?id=102998

also in latest stable - 15.0.874.120 m

[chro...@googlecode.com]

Comment #4 on issue 102998 by a...@storpool.com: SVG animation flickering
https://code.google.com/p/chromium/issues/detail?id=102998

Thank you.
I will create a frame with the entire issue on the wall and point to it
when someone asks me why I am not using Chrome anymore.

I do agreee that after 3 years and 4 months a lot of things changed.

with no regards,
Anton Todorov

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: ExternalDependency
Owner: ---
Cc: dstoc...@chromium.org p...@chromium.org

Comment #5 on issue 102998 by p...@chromium.org: SVG animation flickering
https://code.google.com/p/chromium/issues/detail?id=102998

a...@storpool.com, I don't understand why your reply was so hostile. I
checked as well and your example seems to work properly now. Are you still
seeing the bug or.. what's up?

[chro...@googlecode.com]

Comment #6 on issue 102998 by atodo...@packetscale.com: SVG animation
flickering
https://code.google.com/p/chromium/issues/detail?id=102998

Sorry for the previous note was sent from other profile.

I am the guy who reported the bug.

> I don't understand why your reply was so hostile.

I will try to explain why i am so frustrated.

Please check the time-line again.

nov 4 2011 issue reported
- no response
nov 16 2011 reproduced in latest build (15.0.874.120 m)
- no response
mar 10 2013 relabeled by bugd...@chroimum.org
- I am not sure is it human or bot
mar 19 2015 response that you can't reproduce the bug in the current build

I've hit the issue while developing statistics reporting web interface for
a customer's project. The project is for a long time over.

But please check the time-line again - it is more than 3 years later and:

I do not know is the bug tracked when reported.
I do not know is the bug handled, tested and scheduled for fix
I do not know when the bug is fixed.
I do not know how the bug is fixed - bug-fix or thanks to the project
redesign and development over the time.

So in other words for me it is looking like - I am reporting bug in Galaxy
Nexus and I have response *3+ years* later that the bug is not reproducible
on current Nexus 9.

> Are you still seeing the bug or.. what's up?

I can confirm that with the current stable the bug is not reproducible.
You can archive the ticket.

---
Anton Todorov