Feature Request: Add alert dialog detection and handling capabilities

[wzrazsh]

Is your feature request related to a problem? Please describe.

I'm working on a web automation project using Chrome DevTools MCP and encountered a significant limitation when dealing with JavaScript alert dialogs. When my automation script encounters an alert() call in the target page, the entire automation process gets blocked because there's no way to detect or handle these dialogs programmatically.

This is particularly problematic when testing web applications that use alert dialogs for user notifications or error messages. The automation script hangs indefinitely waiting for user interaction that will never happen in an automated environment.

Describe the solution you'd like

I would like to see the Chrome DevTools MCP add the following capabilities:

1. Dialog Detection API: A way to detect when JavaScript dialogs (alert, confirm, prompt) appear on the page
2. 2. Dialog Handling Methods: Functions to programmatically accept, dismiss, or interact with these dialogs
3. 3. Event-based Notification: An event system that notifies when dialogs appear, allowing for immediate response
      Proposed API additions:

• handle_dialog(action, promptText?) - Handle the currently active dialog
• • wait_for_dialog(timeout?) - Wait for a dialog to appear
• • • Dialog event listeners for real-time detection
      This would enable robust automation workflows that can handle unexpected dialog interruptions gracefully.

Describe alternatives you've considered

Alternative approaches I've considered:

1. Page-level JavaScript injection: Overriding window.alert, window.confirm, and window.prompt functions to intercept calls. However, this approach has limitations:
2. • Doesn't work for dialogs triggered by browser extensions or system-level alerts
3. • May interfere with the application's intended behavior
4. • Requires careful implementation to avoid breaking existing functionality
5. Polling-based detection: Periodically checking for dialog presence using JavaScript. This is unreliable and inefficient:
6. • High resource consumption due to constant polling
7. • May miss dialogs that appear and disappear quickly
8. • Not a real-time solution
9. Using external automation tools: Integrating with other browser automation frameworks that have dialog handling capabilities. This adds complexity:
10. • Requires maintaining multiple tool integrations
11. • Increases the overall system complexity
12. • May introduce compatibility issues
      The native Chrome DevTools MCP integration would be the most elegant and reliable solution.

Additional context

No response

[OrKoN]

Hi, thanks for reporting. chrome-devtools-mcp already has the dialog handling tool https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md#handle_dialog and all other tools would include the presence of the dialog in the output once it is detected. We would not want to have a wait_for_dialog tool because the clients would need to call it every time to make use of it. Could you please clarify if there is a scenario in which the current dialog handling did not work for you?