Skip to content

fix: re-establish focus after navigation for WebKit keyboard nav test #193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JesperDramsch merged 1 commit into from
Jan 7, 2026
Merged

fix: re-establish focus after navigation for WebKit keyboard nav test #193

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions tests/e2e/specs/search-functionality.spec.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -451,10 +451,17 @@ test.describe('Search Functionality', () => {

await page.waitForFunction(() => document.readyState === 'complete');

// Tab through results
// WebKit requires focus to be explicitly established after page navigation
// before Tab key navigation works correctly. Without this, WebKit returns
// focus to BODY when Tab is pressed. Re-focus on the search input (which
// now contains the query) to establish a proper focus context.
const searchInputAfterNav = await getVisibleSearchInput(page);
await searchInputAfterNav.focus();

// Tab to the next focusable element
await page.keyboard.press('Tab');

// Check if a result link is focused
// Check if a focusable element is focused (could be button, link, or input)
const focusedElement = await page.evaluate(() => document.activeElement?.tagName);
expect(['A', 'BUTTON', 'INPUT']).toContain(focusedElement);
});
Expand Down