chromedevtools--chrome-devtools-mcp
Ashutosh Kumar
496ab1b45f
## Summary Enhances wait_for to support waiting on multiple possible texts and resolve when any one appears. This addresses long-running flows that can end in different UI outcomes (for example, "Complete" or "Error"), avoiding unnecessary 300s waits when only one expected string is provided. Closes #916. ## Tool Update ### wait_for Waits for text on the selected page, now with any-match support. | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | text | string \| string[] | yes | A single text or a non-empty list of texts. Resolves when any value appears. | | timeout | integer | no | Maximum wait in ms (0 keeps default behavior). | --- ## Design / Implementation - Kept backward compatibility: existing single-string text calls continue to work unchanged. - Added schema support for string | string[] with non-empty array validation. - Updated context API to accept string | string[]. - Matching logic now normalizes to an array and races all candidates across all frames using both: - aria/<text> - text/<text> - Added clearer response output for array input: - Element matching one of ["Complete","Error"] found. - Updated generated tool docs for the new wait_for contract. - Improved docs generation to render ZodUnion types (so union params are documented correctly, not as unknown). --- ## Tests Added/updated coverage for: - Schema acceptance of: - single string - non-empty string array - rejection of empty array - Any-match array success case - Any-match array when matching text appears later (async/delayed content) - Existing wait_for behavior remains covered for single-text usage Executed relevant test suites: - tests/tools/snapshot.test.ts - tests/McpContext.test.ts - tests/index.test.ts Confirmation after the change applied: https://opncd.ai/share/8m6I4r4a