From 43a97878ce14b72f0981164f87f2e35e14151312 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sun, 7 Apr 2024 11:22:09 +0200
Subject: Adding upstream version 110.0.1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 .../nodes/Element-setAttribute-crbug-1138487.html  | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 testing/web-platform/tests/dom/nodes/Element-setAttribute-crbug-1138487.html

(limited to 'testing/web-platform/tests/dom/nodes/Element-setAttribute-crbug-1138487.html')
diff --git a/testing/web-platform/tests/dom/nodes/Element-setAttribute-crbug-1138487.html b/testing/web-platform/tests/dom/nodes/Element-setAttribute-crbug-1138487.html
new file mode 100644
index 0000000000..9aa9ed8139
--- /dev/null
+++ b/testing/web-platform/tests/dom/nodes/Element-setAttribute-crbug-1138487.html
@@ -0,0 +1,22 @@
+<!DOCTYPE html>
+<script src="/resources/testharness.js"></script>
+<script src="/resources/testharnessreport.js"></script>
+<script>
+// Regression test for crbug.com/1138487.
+//
+// It was possible for a non-ASCII-lowercase string to be used when inserting
+// into the attribute collection if a hashtable encountered it during probing
+// while looking for the ASCII-lowercase equivalent.
+//
+// This caused such a string to be illegally used as an attribute name, thus
+// causing inconsistent behavior in future attribute lookup.
+test(() => {
+  const el = document.createElement('div');
+  el.setAttribute('labelXQL', 'abc');
+  el.setAttribute('_valueXQL', 'def');
+  assert_equals(el.getAttribute('labelXQL'), 'abc');
+  assert_equals(el.getAttribute('labelxql'), 'abc');
+  assert_equals(el.getAttribute('_valueXQL'), 'def');
+  assert_equals(el.getAttribute('_valuexql'), 'def');
+}, "Attributes first seen in mixed ASCII case should not be corrupted.");
+</script>
-- 
cgit v1.2.3

