1) [Chrome] › playwright/e2e/accessibility/keyboard-navigation.spec.ts:106:5 › Landmark navigation tests › without an open room Error: expect(locator).toBeFocused() failed Locator: locator('.mx_HomePage') Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for locator('.mx_HomePage') 7 × locator resolved to <main tabindex="-1" class="mx_AutoHideScrollbar mx_HomePage mx_HomePage_default">…</main> - unexpected value "inactive" 140 | // Pressing Control+F6 again will focus the home section 141 | await page.keyboard.press("ControlOrMeta+F6"); > 142 | await expect(page.locator(".mx_HomePage")).toBeFocused(); | ^ 143 | 144 | // Pressing Control+F6 will bring focus back to the space button 145 | await page.keyboard.press("ControlOrMeta+F6"); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/accessibility/keyboard-navigation.spec.ts:142:52

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

1 skipped 130 passed (10.5m)

3 skipped 130 passed (11.7m)

1 flaky [Chrome] › playwright/e2e/accessibility/keyboard-navigation.spec.ts:106:5 › Landmark navigation tests › without an open room 134 passed (13.0m)

1 skipped 6 passed (24.2s)