WebDriver UDF - Help & Support (III)

[mLipok]

I had an issue with one of my script.
I found that --log-path can not be set to a path longer than 100 chars.
I was looking over internet and I was not able to find this restriction/requirment.

Could somebody confirm that --log-path have limited filepath length to 100 chars?
Colud somebody point me to proper reference documenation which will show this restriction ?

Edited December 9, 2021 by mLipok

[Danp2]

@mLipok

1. Not everyone is going to know which webdriver you use on a daily basis, so excluding that detail may limit your responses
2. This may be better suited as it's own discussion as it doesn't really involve the Webdriver UDF
3. You may be better off posting your question here

P.S. What were the symptoms of a path > 100 chars (how did you know it wasn't working)?

[TheDcoder]

1 hour ago, Danp2 said:

Not everyone is going to know which webdriver you use on a daily basis, so excluding that detail may limit your responses

At this point the ChromeDriver is a de-facto standard in web automation

No offense to other browsers... I use it because I get to access the powerful CDP features as well.

About the path string length limitation, I think we can bypass it by using a relative path and setting the destination folder as the working directory when starting the driver

[mLipok]

 

On 12/10/2021 at 2:16 AM, Danp2 said:

@mLipok

1. Not everyone is going to know which webdriver you use on a daily basis, so excluding that detail may limit your responses
2. This may be better suited as it's own discussion as it doesn't really involve the Webdriver UDF
3. You may be better off posting your question here

P.S. What were the symptoms of a path > 100 chars (how did you know it wasn't working)?

I asked about general problem with "--log-path" and your's related question helped me to understand the clue of the problem.

So here is my example:

expandcollapse popup

#include <MsgBoxConstants.au3>

#include "wd_capabilities.au3"
#include "wd_helper.au3"

_Example_UsingCapabilitesWithChrome()
If @error Then ConsoleWrite("! ---> @error=" & @error & "  @extended=" & @extended & _
        " : Error launching browser" & @CRLF)

Func _Example_UsingCapabilitesWithChrome()
    _WD_CapabilitiesStartup()
    _WD_CapabilitiesAdd("alwaysMatch")
    _WD_CapabilitiesAdd("acceptInsecureCerts", True)
    _WD_CapabilitiesAdd("firstMatch", "chrome")
    _WD_CapabilitiesAdd("w3c", True)
    _WD_CapabilitiesDump(@ScriptLineNumber & " Testing")
    Local $sCapabilities = _WD_CapabilitiesGet()

    _WD_Option("Driver", @ScriptDir & "\chromedriver.exe")
    _WD_Option("Port", 9515)
    _WD_Option("DefaultTimeout", 1000)
    Local $sLog_Dir = 'C:\Testing_LogDir_'
    Local $sLog_Name = '\WebDriver_Testing.log'
    While 1
        $sLog_Dir &= 'a'
        If StringLen($sLog_Dir & $sLog_Name) > 200 Then ExitLoop
    WEnd
;~  DirCreate($sLog_Dir)

    ConsoleWrite("! LogPath = " & $sLog_Dir & $sLog_Name & @CRLF)
    ConsoleWrite("! LogPath Length = " & StringLen($sLog_Dir & $sLog_Name) & @CRLF)

    _WD_Option("DriverParams", "--log-path=" & Chr(34) & $sLog_Dir & $sLog_Name & Chr(34))

    _WD_Startup()
    If @error Then Return SetError(@error, @extended, "")

    Local $WD_SESSION = _WD_CreateSession($sCapabilities)
    If @error Then Return SetError(@error, @extended, $WD_SESSION)

    ; this MsgBox is placed here only to have possibility to manually check if all is fine with Chrome instance
    If Not @Compiled Then MsgBox($MB_OK + $MB_TOPMOST + $MB_ICONINFORMATION, "Information #" & @ScriptLineNumber, "Waiting before _WD_Shutdown()")

    _WD_DeleteSession($WD_SESSION)
    _WD_Shutdown()
EndFunc   ;==>_Example_UsingCapabilitesWithChrome

Conclusion:
There is no problem with WebDriver API.

The solutions is to uncomment:

;~  DirCreate($sLog_Dir)

The problem is on user or UDF side. One of them should check if Directory exist and is accesible.


btw.
Sorry but yeasterday I was really tired (was working in my office 14 hour) and thus my post was not well written.

 

 

Edited December 12, 2021 by mLipok

[Letraindusoir]

17 hours ago, Danp2 said:

@LetraindusoirCheck out the coding for _WD_ElementSelectAction.

P.S. Are you using the latest version? I'm guessing not based on the code you posted.

Yes, I am now using the last version that is not the latest one

I have seen '_WD_ElementSelectAction'  ,but not very understand,

Because parameters in  '_WD_ElementSelectAction'  are all formal parameters, not specific application scenarios

[Letraindusoir]

16 hours ago, mLipok said:

 this mean:

Local $sElement_Form = _WD_FindElement($sSession, $_WD_LOCATOR_ByXPath, '//form') ;; start looking for "form" element from the root element of the document
Local $sElement_Input = _WD_FindElement($sSession, $_WD_LOCATOR_ByXPath, '//input', $sElement_Form) ;; start looking for "input" element from $sElement_Form

 

I seem to understand it.

$sSelector is a child element and $sStartElement is the parent element.

Similar to that of the jquery : $('StartElement').find('Selector')...

[Danp2]

1 hour ago, mLipok said:

There is no problem with WebDriver API. The problem is on user or UDF side. One of them should check if Directory exist and is accesible.

I'd say that it's the script writer's responsibility to perform these checks. However, the UDF could do a better job of detecting that the webdriver console exited with errors.

1 hour ago, mLipok said:

Sorry but yeasterday I was really tired (was working in my office 14 hour) and thus my post was not well written.

No worries. Just don't let it happen again! 😜

[mLipok]

48 minutes ago, Danp2 said:

However, the UDF could do a better job of detecting that the webdriver console exited with errors.

It does:

Quote

__WD_Post: StatusCode=0; ResponseText=WinHTTP request timed out before Webdriver...
__WD_Post ==> Send / Recv error: WinHTTP request timed out before Webdriver
_WD_CreateSession: WinHTTP request timed out before Webdriver
_WD_CreateSession ==> Webdriver Exception: HTTP status = 0
! ---> @error=10  @extended=0 : Error launching browser
>Exit code: 0    Time: 2.88
 

But I had to gues, search to know what the real problem was.

 

Edited December 10, 2021 by mLipok

[Danp2]

@mLipokActually, it doesn't, at least not in the way I meant. You are detecting the failure in _WD_CreateSession. I was suggesting that it could be done sooner in _WD_Startup, which uses Run() to launch the web driver, but it doesn't perform any further checks to make sure that the app hasn't exited with an error code.

[mLipok]

I have an issue with using WebDriver I need to use this UDF in headles mode.

Is there a way to handle this kind of pop up message ?

I need to know when it happend and display to EndUser speciall message that he must change the password manually and start processing again.

[Danp2]

@mLipokNot a lot for us to go on there. What have you tried? I would suggest _WD_Alert, but I'm assuming that you've already tried that.

[mLipok]

2 minutes ago, Danp2 said:

I would suggest _WD_Alert, but I'm assuming that you've already tried that.

As so far no.
Never used.
Will try.

[TheDcoder]

_WD_Alert should do the trick, and if it doesn't you can always inject JavaScript to hijack the popup function:

window.alert = Function.prototype.bind();

window.alert is the browser function to display a popup like that, and my code creates a new dummy function which does nothing and replaces that with the browser function.

[mLipok]

On 11/28/2021 at 10:17 PM, mLipok said:

I'm not asking about zooming document, but browser, and if you check then you notice that this are 2 different things.

I found some reference and example which can be used to build an WD_** function which will give current zoom ratio.
https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio#example

https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio#monitoring_screen_resolution_or_zoom_level_changes

Here are an interesting examples:
https://stackoverflow.com/questions/16541676/what-are-best-practices-for-detecting-pixel-ratio-density

Just simple it is a need to check:

Quote

window.devicePixelRatio

 

and AutoIt example:

Func _WD_GetDevicePixelRatio($sSession)
    Local Const $sFuncName = "_WD_GetDevicePixelRatio"
    Local $sResponse = _WD_ExecuteScript($sSession, "return window.devicePixelRatio", Default, Default)
    If @error <> $_WD_ERROR_Success Then _
            Return SetError(__WD_Error($sFuncName, $_WD_ERROR_Exception), "")

    Local $oJSON = Json_Decode($sResponse)
    Local $iResult = Json_Get($oJSON, "[value]")
    Return SetError($_WD_ERROR_Success, 0, $iResult)
EndFunc   ;==>_WD_GetDevicePixelRatio

 

Edited December 18, 2021 by mLipok

[mLipok]

I have such issue:

Ist there a way to return new different @ERROR in the case storage is locked ?

Edited December 31, 2021 by mLipok

[Danp2]

IDK without more details. Is this occurring with _WD_CreateSession? What data is being returned from Chromedriver to __WD_Post?

[mLipok]

Can anyone give an example of how to use:
_WD_ExecuteScript() with $bAsync = True

?

Reading the code of this UDF, I'm just guessing that this function doesn't seem to work.
I'd like to take care of it.
But I have no idea how to use it at all, because I don't know what to use it for.

[TheDcoder]

17 minutes ago, mLipok said:

Can anyone give an example of how to use:
_WD_ExecuteScript() with $bAsync = True

I had to read the W3C spec to find out how async is different from sync execution. Turns out it's not very different from the sync version, the only difference is that your code gets an extra function argument (which is appended to the special arguments array) that you can call to signal that the script is done, you can also supply a value to this function which will be set as the return value.

Here's the demo code I used to test this:

_WD_ExecuteScript($sSession, 'setTimeout(() => arguments[0]("foobar"), 3000)', True)

This does the same thing as:

_WD_ExecuteScript($sSession, 'return "foobar"')

but with a delay of 3 seconds.

This feature is only useful in complex scripts which require waiting for something on the web-page.

Edited January 1, 2022 by TheDcoder
Forgot to disable async in 2nd snippet

[mLipok]

in: _WD_GetFrameCount() what mean: 

Quote

; Remarks .......: The function will not traverse to nested frames

?

Edited January 2, 2022 by mLipok

[Danp2]

@mLipok I would interpret that to mean that frames located within another frame would not be included in the count.