Danp2

This particular code hasn't changed in over four years, so you must have been previously using a *really* old version. The above could be read to indicate that the UDF isn't W3C compliant. Was that your intended meaning? If so, please elaborate on how it doesn't comply with the W3C Webdriver specs. P.S. IIRC, there are multiple examples on this forum for sending keystrokes using _WD_Action.

Looks like you are the same person that opened a GH issue for this. I'm not able to test this currently, but I don't believe this is due to a bug in the UDF. What version of the Edge webdriver are you using?

@CodeWriter Perhaps you misunderstood the current state of things. Here's a quick rundown -- The PR I linked has been proposed by another user The PR hasn't been merged yet because I haven't verified its functionality It will be included in a future release after it has been merged into the main branch The fix is fairly simple, so you are can certainly modify your local copy of the UDF to test it yourself.

https://github.com/Danp2/au3WebDriver/pull/548

@CodeWriter I haven't had time to investigate. PRs are obviously welcome. 😉

You mentioned _WD_Navigate not working, but this function doesn't appear in your code. Please explain. Also, you should show us the console output to allow better understanding of the issue.

Latest update just released. See below for change log.

Technically, it can be launched separately without geckodriver, but the correct parameters need to be utilized so that it behaves the same as when launched via the webdriver. I don't remember the exact parameters, but I used to do this so I know it is possible. I think a search of the forum (and maybe the wiki) would provide the information.

FWIW, there are several functions included in wd_helper.au3 for interacting with Select elements -- _WD_ElementOptionSelect _WD_ElementSelectAction

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.