getAttribute return values incorrectly affected by SMIL animations for some attributes
Reported by
bzbar...@mit.edu,
Jun 22 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Load testcase 2. Look at the resulting alert What is the expected behavior? Alert shows "PASS" What went wrong? Alert shows "FAIL" Did this work before? N/A Does this work in other browsers? Yes Chrome version: 61.0.3135.4 (Official Build) dev (64-bit) Channel: n/a OS Version: OS X 10.12 Flash Version: Shockwave Flash 26.0 r0 This works fine in Firefox and Safari. The SMIL spec is pretty clear: https://www.w3.org/TR/2001/REC-smil-animation-20010904/#BasicAnim says: When an animation is running, it should not actually change the attribute values in the DOM.
,
Jun 27 2017
Able to reproduce the issue on Windows 10, Mac 10.12.5 and Ubuntu 14.04 using chrome reported version #61.0.3135.4 and latest canary #61.0.3141.0. Bisect Information: ===================== Good build: 35.0.1860.0 Revision(253305) Bad Build : 35.0.1861.0 Revision(253549) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/73eb4fedbcf0826ade8b4ce7a1bb8a21eef6e625..403ce3f3f97cc57a4227c75ba9b780667c566d3f From the above change log unable to find an appropriate owner for this issue. Could anyone from dev team please help us in assigning it to the right owner. Hence, marking it as untriaged for further inputs from dev team. Thanks...!!
,
Jul 6 2017
,
Jul 7 2017
,
Jul 7 2017
Bugs that regressed years ago are not regressions. There is a WebKit roll in that regression range but it does not contain any changes that might cause this, as best as I can tell.
,
Jul 7 2017
1ea6a232b0d2b355896cb382e53a236d760cc672 is likely what cause the behavior of the TC to change. The behavior as such likely stems from something else though (SVGProperty rewrite?)
,
Jul 9
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 9
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by manoranj...@chromium.org
, Jun 26 2017