summaryrefslogtreecommitdiffstats
path: root/layout/style/crashtests/1265611-1.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 00:47:55 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 00:47:55 +0000
commit26a029d407be480d791972afb5975cf62c9360a6 (patch)
treef435a8308119effd964b339f76abb83a57c29483 /layout/style/crashtests/1265611-1.html
parentInitial commit. (diff)
downloadfirefox-26a029d407be480d791972afb5975cf62c9360a6.tar.xz
firefox-26a029d407be480d791972afb5975cf62c9360a6.zip
Adding upstream version 124.0.1.upstream/124.0.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'layout/style/crashtests/1265611-1.html')
-rw-r--r--layout/style/crashtests/1265611-1.html24
1 files changed, 24 insertions, 0 deletions
diff --git a/layout/style/crashtests/1265611-1.html b/layout/style/crashtests/1265611-1.html
new file mode 100644
index 0000000000..df5467ffa3
--- /dev/null
+++ b/layout/style/crashtests/1265611-1.html
@@ -0,0 +1,24 @@
+<!DOCTYPE html>
+<!--
+ NOTE: The comment below is no longer quite true - in particular, we've
+ removed the 'layout.css.prefixes.webkit' pref entirely, so this test doesn't
+ exercise the same codepath that it did when the below comment was written. We
+ might as well keep this crashtest, though, even if it traverses a different
+ codepath now.
+-->
+<!--
+ This test relies on triggering a transition on the 'color' property which,
+ at least when this test was written, would trigger a transition on the
+ -webkit-text-fill-color property since its default value is 'currentcolor'.
+
+ However, in crashtests.list we turn off layout.css.prefixes.webkit so
+ we should not trigger a transition on -webkit-text-fill-color.
+ [Alert: This is no longer accurate, per NOTE above.]
+
+ This test exercises some code that, prior to this bug, would fail because we
+ would initially create the transition on -webkit-text-fill-color (because we
+ forgot to check if it was enabled or not) and then we would call other
+ methods that *do* check for the enabled-ness of the property leaving us
+ in an unexpected state.
+-->
+<body style="transition: all 4s" onload="document.body.style.color = 'green';"></body>