Timeout argument not used in ``Promise to wait for download`` keyword in specific case

[MarvKler]

Describe the bug
I am using the keyword Promise to wait for download and i am setting the keyword argument download_timeout to 30 seconds. My default browser timeout is set to 10 seconds -> means: the given timeout as keyword argument is set higher than the normal browser timeout which is used by default.

Now, when executing the test case, the actual download takes more that 10 seconds (approx. 15-20 seconds), but the keyword fails with the message:

TimeoutError: page.waitForEvent: Timeout 10000ms exceeded while waiting for event "download"
=========================== logs ===========================
waiting for event "download"
============================================================

It seems like my given argument value of 30 seconds is not used at all during the keyword execution.

To Reproduce
Steps to reproduce the behavior:

• see description

Expected behavior
The keyword accepts the given argument value of 30 seconds and uses this a timeout for the download promise.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: iOS
• Browser: chrome
• RF-Browser Version: 19.14.2

Additional context
Add any other context about the problem here.

[aaltat]

Please upgrade to the latest version and give it a try. Also could you show me an example with arguments as clear values which shows the problem.

[MarvKler]

Tried it with v20.4, but its still failing.

We are using our own python function as plugin for the browser library - the function looks like:

@keyword
def click_and_wait_for_download(self, locator: str, file_name: str = "", timeout: timedelta = timedelta(seconds=15)) -> DownloadInfo:
    download_promise = self.library.promise_to_wait_for_download(file_name, download_timeout=timeout)
    self.library.click(locator)
    file_object: DownloadInfo = self.library.wait_for(download_promise)
    return file_object

Within the test case in RF we have set the timeout argument to 30s - like:

Click And Wait For Download    locator=#download-btn    file_name=${OUTPUT_DIR}${/}file.mp4    timeout=30s

[MarvKler]

@aaltat any updates on that ?
I have verified this issue again and currently it leads to failing tests, because some of our downloads take more than 10s which is set as our default browser timeout