Leaderboard

Try this instead -- $aElements = _WD_FindElement($oFF, $_WD_LOCATOR_ByXPath, "//div[contains(@title,'Main Server Room')]", Default, True) Formatting should be good cause I just modified your version. 😄

Coding looks goodfor the most. But with $booolNewIPSdata in callback function you do not get all informations coming from DLL. I think this could be because the callback function is called again while you are still in this function. You have to leave the callback function as fast as possible. I'm quite sure this is an AutoIt error, because for example the new $str points to another location than the old $str.

The problem could be related to AutoIt, your implementation of the APIs, or both. Unless one is already familiar with the EAPI APIs, which I am not, it's hard to tell without the API documentation (that hopefully includes example code) and/or source code (to see header file declarations).

Google is your friend https://docs.microsoft.com/en-us/windows/win32/shell/app-registration

You should be able to use _WD_FindElement with the correct selector to locate the desired element(s). Can the target email appear more than once in the webpage?

I was able to run a basic command and get a response -- { "id": "1", "method": "Browser.getVersion" } { "id": "1", "result": { "protocolVersion": "1.3", "product": "Firefox", "revision": "1", "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0", "jsVersion": "1.8.5" } } Now just need to figure out which commands are supported by Firefox. FWIW, it doesn't appear to recognize Page.addScriptToEvaluateOnNewDocument as a valid method.

Yes like this : Local $colButtons = _IETagNameGetCollection($oIE, "button") MsgBox($MB_SYSTEMMODAL, "", $colButtons.length & "/" & @error) Local $oButton For $i = $colButtons.length-1 to 0 Step -1 $oButton = $colButtons.item($i) MsgBox($MB_SYSTEMMODAL, "", $oButton.GetAttribute("class") & "/" & $oButton.innerText) ConsoleWrite ($oButton.className & @CRLF) Next

What's New in Version 0.2021.4.22 Fixed: timestamp URL changed, so updated to a working URL, and moved the value from internally hard coded, to the INI file where it can be changed without having to recompile.

This spreadsheet shows that that Page.addScriptToEvaluateOnNewDocument is supposed to be working. 🤔 Edit: I was able to get it partially working by using the websocket for an individual tab instead of the main browser websocket. I say partially because it runs without errors, but it doesn't seem to work when I open a new tab.