-
Notifications
You must be signed in to change notification settings - Fork 14
Description
Current Behavior:
When attempting to automate a selection in a custom dropdown (specifically the ones used by Greenhouse job boards, which appear to be built with react-select), the following sequence occurs:
browser_click on the dropdown control successfully opens the menu.
browser_snapshot shows the listbox and option elements exist in the DOM with valid IDs (e.g., #react-select-3-option-0).
A subsequent browser_click targeting the option selector fails with Error: Element not found, or the menu closes immediately before the click can be registered.
Using browser_type with the option name + \n into the dropdown input often results in "No options" or fails to commit the selection.
Expected Behavior:
The tool should be able to click and select an option within an ARIA listbox without the menu closing prematurely or failing to locate the transient element.
Environment:
Backend: different-ai/opencode-browser
Site: [job-boards.greenhouse.io](tauri://localhost/job-boards.greenhouse.io) (Scale AI, etc.)
Component Type: react-select / ARIA listbox
Steps to Reproduce:
Navigate to a Greenhouse job application.
Use browser_click on a dropdown (e.g., "Gender" or "Work Authorization").
Try to use browser_click on the resulting option selector visible in the snapshot.
Suggested Enhancement:
Implement a more robust "wait-and-click" or focus-locking mechanism for transient UI elements, or add a specialized browser_select_aria tool that handles the specific interaction patterns of ARIA-compliant custom selects.