2) [chromium] › tests/frontend-new/specs/unordered_list.spec.ts:79:13 › unordered_list.js › Pressing Tab in an UL increases and decreases indentation › indent and de-indent list item with keypress Error: locator.selectText: Element is not attached to the DOM Call log: - attempting selectText action - waiting for element to be visible 85 | 86 | // select this text element > 87 | await $firstTextElement.selectText(); | ^ 88 | 89 | const $insertunorderedlistButton = page.locator('.buttonicon-insertunorderedlist'); 90 | await $insertunorderedlistButton.click(); at /home/runner/work/ep_subscript_and_superscript/ep_subscript_and_superscript/src/tests/frontend-new/specs/unordered_list.spec.ts:87:37

1) [chromium] › tests/frontend-new/specs/undo.spec.ts:36:9 › undo button › undo some typing using a keypress Error: expect(locator).toHaveText(expected) failed Locator: locator('#innerdocbody').locator('div').first() Expected: "" Received: "fo" Timeout: 20000ms Call log: - Expect "toHaveText" with timeout 20000ms - waiting for locator('#innerdocbody').locator('div').first() 24 × locator resolved to <div class="ace-line" id="magicdomid12" aria-live="assertive">…</div> - unexpected value "fo" 52 | await page.waitForTimeout(1000) 53 | > 54 | await expect(firstTextElement).toHaveText(originalValue!); | ^ 55 | }); 56 | }); 57 | at /home/runner/work/ep_subscript_and_superscript/ep_subscript_and_superscript/src/tests/frontend-new/specs/undo.spec.ts:54:40

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/