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

WebKit requires focus to be explicitly set after page navigation before
Tab key navigation works correctly. Without this, pressing Tab results
in focus going to BODY instead of the next focusable element.

The fix re-focuses on the search input after form submission navigates
to the search results page, establishing a proper focus context before
pressing Tab to navigate to the next element.

Author: JesperDramsch

tests/e2e/specs/search-functionality.spec.js

@@ -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);
     });