Danp2

I suspect that the issue is associated with this line. Hint: If the path isn't valid, then chromedriver won't load correctly.

Did you check the wiki? https://www.autoitscript.com/wiki/WebDriver#FAQ Did you launch the browser with any special parameters?

Normally, I would say use _WD_Alert. But that isn't possible here since this error is occurring during a call to _WD_LoadWait. You could try calling _WD_Alert before _WD_LoadWait.

Must be something different on your end because it works just fine for me with the double backslash. 🤷‍♂️

Are you sure? What error did you receive? Also, take a look at SetupGecko in wd_demo for an example of using _WD_GetBrowserPath and _WD_CapabilitiesAdd to set the executable path.

There's a FAQ in the wiki for specifying the location of the browser executable -- https://www.autoitscript.com/wiki/WebDriver#FAQ

There have been several recent thread on this topic. For example:

A few key points that I would like you to consider -- I can't speak for others, but I'm not able or willing to provide assistance if you can't stay up-to-date with the latest version of the Webdriver UDF. Similarly, it isn't possible to provide support for older versions of browsers. If it is working with the latest version of Chrome, then it's likely that the problem existed in the older version of Chrome but has been fixed since then by the Chrome developers. I suggest that you read this website. This isn't just directed at you; it's a common issue where people don't take the time to ask the correct question, explain the solution they are actually trying to solve, provide the necessary details, etc. I'm happy to try to assist you further If you do the following -- post a simple script that we can actually run to observe the problem it must utilize the latest version of the Webdriver UDF it must utilize a more recent browser version

That doesn't really help because the date in the header hasn't been updated in two years. The "debuggerAddress" functionality was added since then, so you need to make sure that -- you are using the latest release of the UDF including all of the associated files such as wd_helper.au3, wd_capabilities.au3, etc. you dont have an older copy of these files somewhere that are being accessed instead of the latest versions The bottom line is that you have a configuration issue on your end if you can't successfully run the following line without errors -- _WD_CapabilitiesAdd("debuggerAddress","localhost:9222")

The only explanation for this is that you have an old copy of wd_capabilities.au3 somewhere in your system because this command runs as expected when you include the proper version of the UDF.

Have you tried setting the margins to None?

@abs You should check the value of $sCommand in both scenarios.

This is a derivative of what _WD_Startup does -- Local $sParams = '--port=9515 --verbose --log-path="' & @ScriptDir & '\msedge.log"' Local $sCommand = StringFormat('"%s" %s ', $DriverPath, $sParams) RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $sCommand, "", @SW_SHOW) Untested, but I assume something like this should work ok.

This is the likely source of your issues. If you are going to launch the webdriver like this instead of letting _WD_Startup do it, then you need to adjust the parameter that you are passing to RunAs to include the additional options that are part of DriverParams.

@samibb Sorry, but the problem is clearly in your script and I don't have the patience right now to assist you further. I suggest that you open a separate thread if you still need help.