Adding upstream version 86.0.1.upstream/86.0.1upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 27 insertions, 0 deletions

diff --git a/layout/reftests/svg/smil/style/anim-css-fillopacity-3-clamp-big.svg b/layout/reftests/svg/smil/style/anim-css-fillopacity-3-clamp-big.svg
new file mode 100644
index 0000000000..0faec1156b
--- /dev/null
+++ b/layout/reftests/svg/smil/style/anim-css-fillopacity-3-clamp-big.svg
@@ -0,0 +1,27 @@
+<!--
+   This testcase checks that we don't clamp negative opacity values to their
+   valid range [0,1] until *after* we've done animation & interpolation.
+   If we clamped intermediate results too early (e.g. after parsing, during
+   interpolation, or right after we add the first animation's interpolated
+   value), we'd end up with the wrong intermediate opacity values here.
+ -->
+<svg xmlns="http://www.w3.org/2000/svg"
+     xmlns:xlink="http://www.w3.org/1999/xlink"
+     class="reftest-wait"
+     onload="go()">
+  <style>
+    rect { fill: blue; stroke: black; }
+  </style>
+  <script xlink:href="../smil-grid.js" type="text/javascript"/>
+  <script xlink:href="../smil-util.js" type="text/javascript"/>
+  <script>
+    function go() {
+      var animAttrHashA = { "attributeName" : "fill-opacity",
+                            "from"          : "-0.4",
+                            "by"            : "1.2" };
+      var animAttrHashB = { "attributeName" : "fill-opacity",
+                            "by"            : "0.2" };
+      testAnimatedRectGrid("animate", [animAttrHashA, animAttrHashB]);
+    }
+  </script>
+</svg>