Bug 1931932 [wpt PR 49230] - DOM: Capture apparent getSelection() getter side effects, a=testonly

domfarolino · moz-wptsync-bot · commit 2f84b9fb2f1c · 2024-11-27T16:48:27.000Z
Automatic update from web-platform-tests DOM: Capture apparent getSelection() getter side effects This CL adds tests (and unfortunately, expectations) for a bug that has to do with getters on `getSelection()` having side effects on the internal range maintained by `blink::DOMSelection`, when a selection's anchor node is removed from the DOM. R=masonf Bug: 379275917 Change-Id: Ic69f910b5d070a55a6f0c3992f45c0ad939124d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6026810 Reviewed-by: Mason Freed <masonf@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/main@{#1384416} -- wpt-commits: e60ae5825b9f69af2581e0ae8955f2dbe5e0ebd1 wpt-pr: 49230
diff --git a/testing/web-platform/tests/selection/anchor-removal.html b/testing/web-platform/tests/selection/anchor-removal.html
@@ -0,0 +1,60 @@
+<!DOCTYPE html>
+<html>
+<head>
+<script src='/resources/testharness.js'></script>
+<script src='/resources/testharnessreport.js'></script>
+<script src="/resources/testdriver.js"></script>
+<script src="/resources/testdriver-actions.js"></script>
+<script src="/resources/testdriver-vendor.js"></script>
+</head>
+
+<body>
+</body>
+
+<script>
+async function select_range(t, anchorNode, focusNode) {
+  await new test_driver.Actions()
+      .pointerMove(0, 0, {origin: anchorNode})
+      .pointerDown()
+      .pointerMove(focusNode.clientWidth, focusNode.clientHeight, {origin: focusNode})
+      .pointerUp()
+      .send();
+}
+
+const kHTML = `
+  <div id=parentDiv>
+    <span id=parentParagraph>Parent paragraph</span>
+    <div id=childDiv>
+      <span id=childParagraph1>Child paragraph one</span>
+      <span id=childParagraph2>Paragraph two</span>
+    </div>
+  </div>
+`;
+
+// The two tests below are semantically identical, however after the selection
+// is made but before `remove()`:
+//  - The first test does nothing
+//  - The second test runs asserts on `getSelection()` (before `remove()` is
+//    run).
+//
+// The existence of the `getSelection()` asserts before `remove()` appears to
+// have a side-effect in Chromium browsers. See https://crbug.com/379275917.
+promise_test(async t => {
+  document.body.innerHTML = kHTML;
+  getSelection().removeAllRanges();
+  await select_range(t, parentParagraph, childParagraph1);
+
+  parentParagraph.remove();
+  assert_equals(getSelection().anchorNode, parentDiv, "anchorNode snaps up to parent");
+}, "anchorNode snaps up to parent when removed (no asserts)");
+
+promise_test(async t => {
+  document.body.innerHTML = kHTML;
+  getSelection().removeAllRanges();
+  await select_range(t, parentParagraph, childParagraph1);
+
+  assert_equals(getSelection().anchorNode, parentParagraph.firstChild, "anchorNode before move");
+  parentParagraph.remove();
+  assert_equals(getSelection().anchorNode, parentDiv, "anchorNode snaps up to parent");
+}, "anchorNode snaps up to parent when removed (with asserts)");
+</script>
