[🚀 Feature]: Can we have a better way to handle dialog (alert, prompt) when enabling WebDriver BiDi

[HoaiLinh0908]

Description

I'm currently enabling WebDriver BiDi because of its advantages, but things get complicated when it comes to dialog (like alert, model, and prompt). I have to add a lot of code compared to the Legacy protocol to work with alert
WebDriver BiDi:

  DevTools devTools = ((ChromeDriver) webDriver).getDevTools();
  devTools.createSession();

  // Listen for JavaScript dialogs (alerts, confirms, prompts)
  devTools.send(Page.enable());
  devTools.addListener(Page.javascriptDialogOpening(), dialog -> {
    System.out.println("Alert Text: " + dialog.getMessage());
    devTools.send(Page.handleJavaScriptDialog(true, null)); // Accept the alert
  });

Legacy:

webDriver.switchTo().alert();

It would be nice to have a more user-friendly way to handle alerts, as it is heavily used in almost every project.

Have you considered any alternatives or workarounds?

I'm currently turning off BiDi on tests that contain alerts.

[titusfortner]

@HoaiLinh0908, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then J-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[pujagani]

Hey! @HoaiLinh0908 The code shared is referring to devtools. If you meant that we should consider a better way to handling dialogs when BiDi is enabled, then we do that in our plan as we transition from WebDriver W3C to WebDriver BiDi under the hood.

[github-actions]

This issue was closed because we did not receive any additional information after 14 days.

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.