Fix Selenium tests for updated Chrome Extensions UI

[MiWeiss]

Summary

• Fixed Selenium tests failing due to Chrome Extensions Manager UI changes
• Updated shadow DOM navigation with robust null checking
• Tests now find extension by name instead of assuming DOM structure

Problem

All Selenium tests were failing with:

JavascriptException: Cannot read properties of null (reading 'shadowRoot')

This occurred in the navigate_to_options() function which tried to navigate Chrome's extensions page to find the extension ID. Chrome updated their Extensions Manager UI, breaking the old shadow DOM traversal.

Solution

Rewrote navigate_to_options() with a more robust approach:

Old approach:

• Assumed specific DOM structure
• No null checks
• Clicked details button to get ID from URL

New approach:

• Traverses shadow DOM with comprehensive null checks
• Searches for extension by name ("licenseplate")
• Gets ID directly from element attribute
• More resilient to future UI changes

Code Changes

browser_control/test_chrome.py:

// Now finds extension by searching for its name
const items = itemList.shadowRoot.querySelectorAll('extensions-item');
for (let item of items) {
    if (!item || !item.shadowRoot) continue;
    const nameElement = item.shadowRoot.querySelector('#name');
    if (nameElement && nameElement.textContent.includes('licenseplate')) {
        return item.getAttribute('id');
    }
}

Benefits

1. Robust: Null checks prevent crashes when DOM structure changes
2. Future-proof: Finding by name is more stable than position-based selection
3. Clearer: Intent is obvious - "find extension named licenseplate"
4. Simpler: No need to click buttons and parse URLs

Test Plan

• Verify all 13 Selenium tests pass
• Check that extension options page loads correctly
• Confirm cache tests work properly
• Validate ignore functionality tests pass

Related Issues

Fixes the failing Selenium tests on main branch that started after Chrome updated their Extensions UI.

🤖 Generated with Claude Code