Danp2

As you stated, it's likely an environmental issue on the user's side. I see that you aren't running the latest version of the UDF, so you should probably address that. Does the issue occur with all browsers or only Edge?

Did you try using the method that @SOLVE-SMART previously explained to you regarding how to identify the selector for an element? Please show us what you've tried thus far.

You could try retrieving all of the list item (li) elements. Also, take a look at _WD_GetTable.

You can thanks Google for this. They are modifying the behavior of the website when the browser has been launched via the webdriver. IIRC, there isn't a known way to bypass this. You may want to search the forum for past discussions.

Yes, you can use any type of selector you would like to use. Have you tried using _WD_LinkClickByText?

This is very old. The current release is 1.4.0, which you can download from here. You need to do this as well by manually grabbing the contents of this file and replacing the contents of your current WinHttp.au3. I'm not sure why InetRead is failing for you.

It isn't exactly clear to me why you would be receiving this error message. You may want to share the output from the Scite console. Also, please share the output from this code -- #include "wd_helper.au3" Local Const $sGitURL = "https://github.com/Danp2/au3WebDriver/releases/latest" Local $sRegex = '<a.*href="\/Danp2\/au3WebDriver\/releases\/tag\/(.*?)"' Local $sResult = InetRead($sGitURL, $INET_FORCERELOAD) ;### Debug CONSOLE ↓↓↓ ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') >Error code: ' & @error & @CRLF)

@Jos Good question. I just quickly reviewed my settings, but I don't see where I disabled anything in either extension. I suggest that you try it yourself and see if you encounter any issues.

I've been using VSCode as my primary coding tool for a while, so anything that can be done to improve integration with AutoIt is welcomed. FWIW, I have both of these extensions installed / enabled at the same time, and it's working ok for me.

Pretty sure the issue is the missing HTTP(S) prefix.

Yes, unless you launch the browser executable with the correct parameters so that it is accepting the webdriver commands.

How was the browser originally launched? You won't be able to connect to it if it is the standard browser instance without the remote debugging enabled.

I can see some definite issues with the "wrapper" functions that you wrote. Beyond that, you should review the forum rules regarding gaming.

It's likely that there are more than one elements matching your selector. First step is to confirm that is true. Then adjust your selector so that the correct one is found.

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