[android] Use a system allocated port for WebDriver BiDi
Categories
(Testing :: geckodriver, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
Details
(Whiteboard: [webdriver:backlog])
Similar to Marionette (bug 1240830) we would like to see that the Remote Agent can use a system allocated port on Android. But the problem here is the port forwarding via adb. Given that it is not a basic socket but a WebSocket the port needs to be equal on the host and the device. That means that even if the Remote Agent gets a free port, we might fail on the host side because the port is already in use.
We might be able to do the following:
- Let geckodriver try to find a free port on both the host and the device
- Immediately setup the adb forwarding so that the port on the host is in use and can no longer be acquired by some other service
- Hope that the Remote Agent is able to acquire the requested port - if not kill the browser and try again with step 1.
What's more complex is to use geckodriver as a WebSocket proxy, which is out of scope for now.
|
Reporter | |
Comment 1•2 years ago
|
||
What we actually could use here is a whitelist entry for host/origin for the host so that we not necessarily have to run the adb forward on the same port on the host and device. We would have to wait for bug 1750689.
|
|
Reporter | |
Updated•2 years ago
|
|
||
Updated•2 years ago
|
Description
•