-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: BiDi events are not fired in order #14436
Comments
@joerg1985, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Thank you for raising this. Do you have an example/test that can help reproduce this? |
@pujagani i can only provide some code to show this without a browser, see below. As soon as the I think it should be possible to have this in a real browser as described in the issue.
|
Thank you so much for sharing this! |
What happened?
This is basically the same problem for BiDi as for CDP, see issue #13845
I stumbled into this while implementing network interception, using the
org.openqa.selenium.bidi.module.Network
class.The events raised by the bidi connection are processed concurrently and not raised in order. This will make it hard to use things like
org.openqa.selenium.bidi.module.Network
as there is no guaranteenetwork.responseStarted
is the first event raised for this request.So i think it might be worth looking into this and find a solution, before BiDi does leave the beta stage.
How can we reproduce the issue?
Relevant log output
Operating System
Win 10 x64
Selenium version
4.23.0
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
N/A
The text was updated successfully, but these errors were encountered: