Clamp the presentation time to a usable range

If the time container is seeked to a large enough value, we will end up truncating it to SMILTime::Latest(), which is the largest value that isn't one of the two special values ("indefinite" and "unresolved"). When trying to derive other values from this value - like if we have an interval begin at it - we can end up in a loop since any the result of any additions will yield the same value, leading to the element being rescheduled at the same point in time, hanging UpdateIntervals(). This mechanism can also be used to implement the "once" animation-policy in a slightly nicer way. This will be done as a follow-up. Bug: 1039886 Change-Id: If13d7d7d3c44c4f586d15852eb05105879f44918 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030885 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#737260}
web-platform-tests · Jan 31, 2020 · 0db6154 · 0db6154
1 parent c7227ea
commit 0db6154
Showing 1 changed file with 15 additions and 0 deletions.
diff --git a/svg/animations/end-of-time-crash.html b/svg/animations/end-of-time-crash.html
@@ -0,0 +1,15 @@
+<!DOCTYPE html>
+<html class="reftest-wait">
+<title>Seeking the time container to a large value does not cause a crash (or hang)</title>
+<svg>
+  <rect height="100" width="100" fill="blue">
+    <animateTransform begin="18446744073709551557" dur="2" repeatCount="indefinite"
+                      attributeName="transform" type="rotate" from="0,15,15" to="360,15,15"/>
+  </rect>
+</svg>
+<script>
+  let svg = document.querySelector("svg");
+  svg.setCurrentTime(18446744073709551557);
+  let html = document.documentElement;
+  html.addEventListener("TestRendered", () => html.classList.remove("reftest-wait"));
+</script>