WebDriver UDF - Help & Support (III)

[Danp2]

@mLipok Why 10 seconds? Can't you use a shorter timeout for whatever it is you want to test?

Please explain 🤨

[mLipok]

Ok it may be 5 sec.

Explanation:
I need a publicly accessible web portal that takes long enough to load to show some "problems" of this UDF, and of course, a way to solve it.
 

[Danp2]

@mLipokCould you accomplish this with your own HTML file?

[mLipok]

for _WD_NewTab() function there is parameter:
$sFeatures           - [optional] Comma-separated list of requested features of the new tab

Please provide link to some description or to WebDriver documentation in this regards.

 

[seadoggie01]

4 minutes ago, mLipok said:

for _WD_NewTab() function there is parameter:
$sFeatures           - [optional] Comma-separated list of requested features of the new tab

Please provide link to some description or to WebDriver documentation in this regards.

 

https://developer.mozilla.org/en-US/docs/Web/API/Window/open#window_features

Edit: It's often helpful to check out the internal code... in this case it's nice because it is passed to _WD_ExecuteScript using window.open in JavaScript

Edited August 14, 2021 by seadoggie01

[mLipok]

5 minutes ago, seadoggie01 said:

https://developer.mozilla.org/en-US/docs/Web/API/Window/open#window_features

Thanks,
using the given URL    I just made PR
https://github.com/Danp2/WebDriver/pull/84

 

Edited August 14, 2021 by mLipok

[mLipok]

On 8/11/2021 at 9:44 PM, Danp2 said:

@mLipokCould you accomplish this with your own HTML file?

WIll try with:
 

<script type="text/javascript">
 
setTimeout(function()
{
    // Delayed code in here
    alert('You waited 10 seconds to see me'); // Waits 5 seconds, then alerts this
}, 10000); // 10000 = 10 seconds

</script>

 

Edited August 14, 2021 by mLipok

[_leo_]

Hi there,

I am trying to click an element, but for some reason the standard way does no longer "make" the click. It used to work up until now. (Doubleclick does not work either) When trying to click the button with a javascript command, it works. Could this problem be due to changes in the website's underlying framework? Is there a common solution to such a problem? The website is "society6".

//This finds the element, but the Action does not execute
_WD_WaitElement($sSession, $_WD_LOCATOR_ByXPath, "//button[@class='uploadBtn_banner_2b9z8']")
$add = _WD_FindElement($sSession, $_WD_LOCATOR_ByXPath, "//button[@class='uploadBtn_banner_2b9z8']")
_WD_ElementAction($sSession, $add, 'click')

//This works
_WD_ExecuteScript($sSession, "document.getElementsByClassName('uploadBtn_banner_2b9z8')[0].click()")

Thanks for your help.

 

[Danp2]

1 hour ago, _leo_ said:

Could this problem be due to changes in the website's underlying framework?

Yes... It's possible that the xpath has changed, but can't say for sure since you didn't include the resulting Scite output from when your code ran. Was the element found using that xpath?

P.S. This discussion really belongs in the support thread in the GH&S section (see link below in m sig)

[_leo_]

Quote

Yes... It's possible that the xpath has changed, but can't say for sure since you didn't include the resulting Scite output from when your code ran. Was the element found using that xpath?

@Danp2 Yes, the element is found with xpath, and ElementAction does try to click it. (As commented in the code of my previous post) The output looks exactly the same as a successfull click would look like. It is just very strange to me, that the whole automation stopped working from one day to another. I will try on my other computer too.

 

[Danp2]

@_leo_The website appears to use both jQuery and React javascript libraries. These can be difficult to automate as some underlying events may not get automatically triggered. FWIW, I tried joining the website to take a look but it looks like I can't access that portion of the site without going thru the verification process.

[_leo_]

@Danp2 Thanks for checking. Yes an account is needed to access that part of the website. Do you think there is any point in trying to automate this page with this udf?

[Danp2]

@_leo_You didn't give us the actual URL, so I'm not sure that I even tried the right portion of the site. I did create an account, but I'm not willing to go through their Paypal "verification" process just for testing purposes.

As you've already seen, you can use _WD_Execute to do most anything when necessary.

[ElPandaRojo1]

Hello, I would like to know if there is any way to update only the driver to handle the browser? depending on the version that is installed on the pc?

Sorry if you solved this already but I didn't find anything on this.

[Danp2]

@ElPandaRojo1Take a look at _WD_UpdateDriver.

P.S. This type of question really belongs in the support thread in the GH&S section (see link below in m sig)

[nguyenthaiytcc]

Hi @Danp2,
I'm trying to access website using emulator mode similar to emulator mode in F12 Develope. However, for some websites, I can't do click or touch. I need to solve this problem, hope to get your help. Here is my code:
 

_WD_Option('Driver', @ScriptDir & '\source\chromedriver.exe')
_WD_Option('Port', 9515)
_WD_Option('DriverParams', '--log-path="' & @ScriptDir & '\chrome.log"')
$sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"goog:chromeOptions": {"w3c": true, "excludeSwitches": [ "enable-automation"], "useAutomationExtension": false, "mobileEmulation": { "deviceMetrics": { "width": 640, "height": 360, "pixelRatio": 3.0, "click": true}, "userAgent": "Mozilla/5.0 (Linux; Android 4.2.1; en-us; Nexus 5 Build/JOP40D) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166 Mobile Safari/535.19" }}}}}'
_WD_Startup()
Sleep(2000)
$sSession = _WD_CreateSession($sDesiredCapabilities)
_WD_Navigate($sSession, "https://tdtc88.com/")

 

Edited August 29, 2021 by nguyenthaiytcc

[Danp2]

@nguyenthaiytccThat is a gaming website, so helping you to automate it would be against the forum rules.

[mLipok]

I'm trying to automate: https://www.imsig.pl/
In headless mode all is done well.
But when I try to view what is going on I mean I want to use non headless mode, then I get this problem

Quote

_WD_WaitElement ==> Success
__WD_Post: URL=HTTP://127.0.0.1:9515/session/d8fa72e273d772b3ed19606e53f4acdc/element; $sData={"using":"xpath","value":".//input[@name=\"email\"]"}
__WD_Post: StatusCode=200; ResponseText={"value":{"element-6066-11e4-a52e-4f735466cecf":"7a0b511c-d69f-478b-8218-74f76693465e"}}...
_WD_FindElement: {"value":{"element-6066-11e4-a52e-4f735466cecf":"7a0b511c-d69f-478b-8218-74f76693465e"}}
__WD_Post: URL=HTTP://127.0.0.1:9515/session/d8fa72e273d772b3ed19606e53f4acdc/element/7a0b511c-d69f-478b-8218-74f76693465e/clear; $sData={"id":"7a0b511c-d69f-478b-8218-74f76693465e"}
__WD_Post: StatusCode=400; ResponseText={"value":{"error":"element not interactable","message":"element not interactable\n  (Session info: c...
__WD_Post ==> Element interaction issue: {"value":{"error":"element not interactable","message":"element not interactable\n  (Session info: chrome=92.0.4515.159)","stacktrace":"Backtrace:\n\tOrdinal0 [0x00662DB3+2502067]\n\tOrdinal0 [0x005FC5B1+2082225]\n\tOrdinal0 [0x00502360+1057632]\n\tOrdinal0 [0x0052528B+1200779]\n\tOrdinal0 [0x00545D23+1334563]\n\tOrdinal0 [0x00523446+1193030]\n\tOrdinal0 [0x00545E0A+1334794]\n\tOrdinal0 [0x00554B7B+1395579]\n\tOrdinal0 [0x00545BEB+1334251]\n\tOrdinal0 [0x00522174+1188212]\n\tOrdinal0 [0x00523009+1191945]\n\tGetHandleVerifier [0x007DEC5C+1511084]\n\tGetHandleVerifier [0x00888522+2205554]\n\tGetHandleVerifier [0x006E3393+480739]\n\tGetHandleVerifier [0x006E2579+477129]\n\tOrdinal0 [0x00601E5D+2104925]\n\tOrdinal0 [0x006063F8+2122744]\n\tOrdinal0 [0x00606537+2123063]\n\tOrdinal0 [0x0060EE53+2158163]\n\tBaseThreadInitThunk [0x769EFA29+25]\n\tRtlGetAppContainerNamedObjectPath [0x772E7A7E+286]\n\tRtlGetAppContainerNamedObjectPath [0x772E7A4E+238]\n"}}
_WD_ElementAction: {"value":{"error":"element not interactable","message":"element not interactable\n  (Session info: c...
_WD_ElementAction ==> Element interaction issue: {"value":{"error":"element not interactable","message":"element not interactable\n  (Session info: chrome=92.0.4515.159)","stacktrace":"Backtrace:\n\tOrdinal0 [0x00662DB3+2502067]\n\tOrdinal0 [0x005FC5B1+2082225]\n\tOrdinal0 [0x00502360+1057632]\n\tOrdinal0 [0x0052528B+1200779]\n\tOrdinal0 [0x00545D23+1334563]\n\tOrdinal0 [0x00523446+1193030]\n\tOrdinal0 [0x00545E0A+1334794]\n\tOrdinal0 [0x00554B7B+1395579]\n\tOrdinal0 [0x00545BEB+1334251]\n\tOrdinal0 [0x00522174+1188212]\n\tOrdinal0 [0x00523009+1191945]\n\tGetHandleVerifier [0x007DEC5C+1511084]\n\tGetHandleVerifier [0x00888522+2205554]\n\tGetHandleVerifier [0x006E3393+480739]\n\tGetHandleVerifier [0x006E2579+477129]\n\tOrdinal0 [0x00601E5D+2104925]\n\tOrdinal0 [0x006063F8+2122744]\n\tOrdinal0 [0x00606537+2123063]\n\tOrdinal0 [0x0060EE53+2158163]\n\tBaseThreadInitThunk [0x769EFA29+25]\n\tRtlGetAppContainerNamedObjectPath [0x772E7A7E+286]\n\tRtlGetAppContainerNamedObjectPath [0x772E7A4E+238]\n"}}
 

My capabilities settings are:

{"capabilities":
    {
        "alwaysMatch": 
        {
            "goog:chromeOptions":
            {
                "w3c": true
                ,"args":
                    [
                        "--headless"
                        ,"start-maximized"
                        ,"disable-infobars"
                        ,"user-data-dir=C:\\Users\\Szef\\AppData\\Local\\Google\\Chrome\\User Data\\Default"
                    ]
                ,"prefs":
                    {
                    }
            }
        }   
    }
}

This problem is all the more weird that it occurs on my computer, but on @dPilar computer everything works fine in both modes.

Any sugesstions how to solve this issue on my computer ?

 

Edited August 30, 2021 by mLipok

[Danp2]

@mLipok I would suggest checking the screen resolution of both PCs. It's possible that the website is detecting a smaller window size and attempting to adjust positioning of elements, which could lead to the target element being partially hidden by another one.

[mLipok]

In the meanwhile I did some checking on my side

This particular error was related to the fact that this elemet stay hidden....
So I add Visible+Enabled option:

_WD_WaitElement($_IMSIG__WD_SESSION, $_WD_LOCATOR_ByXPath, './/input[@name="email"]', Default, Default, BitOR($_WD_OPTION_Visible, $_WD_OPTION_Enabled))

and this part of this issue was solved. 
But there was still a problem with the difference between the two modes, so I did further tests.

It turns out that the main problem is clicking:

Local $sElement = _WD_WaitElement($_IMSIG__WD_SESSION, $_WD_LOCATOR_ByXPath, '//div[@class="header-logo"]//a[@href="/konto"]', Default, Default, BitOR($_WD_OPTION_Visible, $_WD_OPTION_Enabled))
    If Not @error Then
        Local $v_Result = _WD_ElementAction($_IMSIG__WD_SESSION, $sElement, 'click')
    EndIf

 

Quote

Headless = False

__WD_Post: URL=HTTP://127.0.0.1:9515/session/6d69c5e66521d64dd113400c90ab7e81/element; $sData={"using":"xpath","value":"//div[@class=\"header-logo\"]//a[@href=\"/konto\"]"}
__WD_Post: StatusCode=200; ResponseText={"value":{"element-6066-11e4-a52e-4f735466cecf":"9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb"}}...
_WD_FindElement: {"value":{"element-6066-11e4-a52e-4f735466cecf":"9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb"}}
__WD_Get: URL=HTTP://127.0.0.1:9515/session/6d69c5e66521d64dd113400c90ab7e81/element/9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb/displayed
__WD_Get: StatusCode=200; $iResult = 0; $sResponseText={"value":true}...
_WD_ElementAction: {"value":true}...
__WD_Get: URL=HTTP://127.0.0.1:9515/session/6d69c5e66521d64dd113400c90ab7e81/element/9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb/enabled
__WD_Get: StatusCode=200; $iResult = 0; $sResponseText={"value":true}...
_WD_ElementAction: {"value":true}...
_WD_WaitElement ==> Success
__WD_Post: URL=HTTP://127.0.0.1:9515/session/6d69c5e66521d64dd113400c90ab7e81/element/9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb/click; $sData={"id":"9d0759e3-9d3c-4aed-8cef-4c4827a2b5cb"}
__WD_Post: StatusCode=200; ResponseText={"value":null}...
_WD_ElementAction: {"value":null}...
__WD_Post: URL=HTTP://127.0.0.1:9515/session/6d69c5e66521d64dd113400c90ab7e81/execute/sync; $sData={"script":"return document.readyState", "args":[]}
__WD_Post: StatusCode=200; ResponseText={"value":"complete"}...
_WD_ExecuteScript: {"value":"complete"}...

Headless = True

__WD_Post: URL=HTTP://127.0.0.1:9515/session/ad38d431b6df5084f1eb4aa7bbc2ce48/element; $sData={"using":"xpath","value":"//div[@class=\"header-logo\"]//a[@href=\"/konto\"]"}
__WD_Post: StatusCode=200; ResponseText={"value":{"element-6066-11e4-a52e-4f735466cecf":"70e87656-84cf-424f-b6a0-eb994354a839"}}...
_WD_FindElement: {"value":{"element-6066-11e4-a52e-4f735466cecf":"70e87656-84cf-424f-b6a0-eb994354a839"}}
__WD_Get: URL=HTTP://127.0.0.1:9515/session/ad38d431b6df5084f1eb4aa7bbc2ce48/element/70e87656-84cf-424f-b6a0-eb994354a839/displayed
__WD_Get: StatusCode=200; $iResult = 0; $sResponseText={"value":true}...
_WD_ElementAction: {"value":true}...
__WD_Get: URL=HTTP://127.0.0.1:9515/session/ad38d431b6df5084f1eb4aa7bbc2ce48/element/70e87656-84cf-424f-b6a0-eb994354a839/enabled
__WD_Get: StatusCode=200; $iResult = 0; $sResponseText={"value":true}...
_WD_ElementAction: {"value":true}...
_WD_WaitElement ==> Success
__WD_Post: URL=HTTP://127.0.0.1:9515/session/ad38d431b6df5084f1eb4aa7bbc2ce48/element/70e87656-84cf-424f-b6a0-eb994354a839/click; $sData={"id":"70e87656-84cf-424f-b6a0-eb994354a839"}
__WD_Post: StatusCode=200; ResponseText={"value":null}...
_WD_ElementAction: {"value":null}...
__WD_Post: URL=HTTP://127.0.0.1:9515/session/ad38d431b6df5084f1eb4aa7bbc2ce48/execute/sync; $sData={"script":"return document.readyState", "args":[]}
__WD_Post: StatusCode=200; ResponseText={"value":"complete"}...
_WD_ExecuteScript: {"value":"complete"}...
 

in both cases (Headless True/False) in the log results looks ok,
but when Headless is OFF (False) then I do not see that this click is done, and because of this the further //input[@name=\"email\"] was keept hidden.

So the question is: Why in case when headless =  False, the Click is not performed well ?

 

Edited August 30, 2021 by mLipok