[🚀 Feature]: Support WebDriver BiDi and "log.entryAdded" events (with Firefox)

[whimboo]

Feature and motivation

With the WebDriver BiDi specification moving forward it would be great to see support for this protocol being added to Selenium. In case of Firefox we already added the log.entryAdded event and relevant commands like session.subscribe to get relevant logging events for console API calls and Javascript exceptions on the page.

Given the high request of Selenium users for such an API it would be great to move the current implementation for Firefox which is based on CDP over to WebDriver BiDi. On our side we have the following bug on file:

https://bugzilla.mozilla.org/show_bug.cgi?id=1753991

CC'ing @AutomatedTester, @shs96c, @titusfortner, @diemol

Usage example

From the user's perspective the API for logging events might not change and could probably the same as when using the CDP backend.

[github-actions[bot]]

@whimboo, 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 I-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, 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!

[diemol]

Added tags for the other bindings so we can track progress.

[whimboo]

@diemol who could potentially could give an update of the current implementation status of this feature in Selenium? Thanks.

[titusfortner]

I don't think we want to track these additions in issues. We should use Puja's more systematic tracking system.

[github-actions[bot]]

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