Page with iframe throws error on TestCafe 1.17.0

What is your Scenario?

TestCafe 1.14.2: When trying to open page on Jira Cloud with iframe everything works fine: TestCafe 1.17.0: When trying to open page on Jira Cloud with iframe it throws error

This problem appears on Jira Cloud.

What is the Current behavior?

On TestCafe 1.17.0 I receive error when navigating to page with iframe

What is the Expected behavior?

I should not receive error when accessing page with iframe (as it is on TestCafe 1.14.2)

What is your public website URL? (or attach your complete example)

My test environment: https://testcafe-example.atlassian.net

What is your TestCafe test code?

import { Selector } from 'testcafe';

fixture('TestCafe - bug on TestCafe 1.17.0').page(
    'https://testcafe-example.atlassian.net/',
);

test.meta({ key: 'testcafe' })(`Problem with iframe`, async (t) => {
    await t
        .click('form#form-login input#username')
        .typeText(
            'form#form-login input#username',
            '[e-mail]',
        )
        .click('form#form-login button#login-submit')
        .typeText('input#password', 'testcafe123!')
        .click('form#form-login button#login-submit');
    await t
        .click('span[aria-label="Settings"]')
        .click('[href$="source=side_nav_find_new_addons"]');
    await t.click('[href$="rtm__get-started"]');
    await t
        .switchToIframe('iframe')
        .expect(Selector('[data-testid="Get-Started-select"]').visible)
        .ok();
});

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

1. Ensure you have TestCafe 1.17.0 installed
2. Login to Jira Cloud
3. Navigate to page with iframe, for example page from app

TestCafe version

1.17.0

Node.js version

No response

Command-line arguments

chrome -e test.ts

Browser name(s) and version(s)

does not matter

Platform(s) and version(s)

No response

Other

No response

[aleks-pro]

Hello @milan-easykad,

There are no updates yet. Once we have any, we will post them here.

[github-actions[bot]]

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don’t have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.