Dan Pollak

[~~Chromium BiDi progress~~](https://docs.google.com/spreadsheets/d/1acM-kHlubpwnW1mFboS9hePawq3u1kf21oQzD16q-Ao/edit?resourcekey=0-PuLHQYLmDJUOXH_mFO-QiA#gid=0) [Outdated] [Mozilla BiDi progress](https://bugzilla.mozilla.org/show_bug.cgi?id=1690255) [Mozilla BiDi status wiki](https://wiki.mozilla.org/WebDriver/RemoteProtocol/WebDriver_BiDi)

Initial coding can be found [here](https://github.com/Danp2/au3WebDriver/tree/dp_bidi)

Here is what I'm currently using to test the new bidi commands -- CLICK ME ```autoit #include "wd_core.au3" #include "wd_capabilities.au3" #include "wd_bidi.au3" ;~ $_WD_Debug = $_WD_DEBUG_Full _WD_CapabilitiesDefine($_WD_KEYS__STANDARD_PRIMITIVE, 'webSocketUrl') _WD_CapabilitiesDefine($_WD_KEYS__STANDARD_PRIMITIVE, '"moz:debuggerAddress"')...

[WPT tracker](https://wpt.fyi/results/webdriver/tests/bidi?label=master&label=experimental&aligned&view=subtest&q=webdriver)

Found that calls to [WinHttpWebSocketReceive](https://learn.microsoft.com/en-us/windows/win32/api/winhttp/nf-winhttp-winhttpwebsocketreceive) would cause the process to hang when there wasn't pending data to receive. Switched to using [websocat](https://github.com/vi/websocat) to perform all websocket activity.

Here is the latest revision of code I'm using to test the new bidi commands -- CLICK ME ```autoit #AutoIt3Wrapper_au3check_parameters=-d -w 1 -w 2 -w 3 -w 4 -w 5...

Honestly, I can't understand what you are trying to say / explain above. I would expect `_WD_CheckContext('')` to fail because you aren't passing it a valid session ID. This is...

That makes no sense to me. Did you post the wrong picture?

Is there a real issue here or pebcak?

> it occured on two different location (pc/client/city). I suggest that you take some time to better define the problem because it's not clear to me what isn't working correctly.