Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestCafe does not have access to data URL iframe #1752

Closed
shhnjk opened this issue Sep 1, 2017 · 4 comments
Closed

TestCafe does not have access to data URL iframe #1752

shhnjk opened this issue Sep 1, 2017 · 4 comments
Labels
STATE: Stale An outdated issue that will be automatically closed by the Stale bot. SYSTEM: hammerhead TYPE: enhancement The accepted proposal for future implementation. TYPE: Web API support
Milestone

Comments

@shhnjk
Copy link

shhnjk commented Sep 1, 2017

Are you requesting a feature or reporting a bug?

Reporting bug.

What is the current behavior?

Accessing data URL iframe fails with error access is denied.

What is the expected behavior?

TestCafe should have access to data URL iframe

How would you reproduce the current behavior (if this is a bug)?

Access data URL iframe with .switchToIframe

Provide the test code and the tested page URL (if applicable)


import { Selector } from 'testcafe';

fixture Getting Started
.page https://test.shhnjk.com/iframer.php?url=data:,test;

test('My first test', async t => {
await t
.switchToIframe("#frame0");

const test = await t.eval(() => document.body.innerText);

await t.expect(text).eql('test');

});

Specify your

  • operating system: Windows 10
  • testcafe version: Latest (downloaded today)
  • node.js version: Latest (downloaded today)
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #9 milestone Sep 1, 2017
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Sep 1, 2017
@shhnjk
Copy link
Author

shhnjk commented Sep 1, 2017

I repro this with Edge. I haven't tested other browsers.

@miherlosev
Copy link
Collaborator

I've created the separate issue in another repository DevExpress/testcafe-hammerhead#1297

@AlexanderMoskovkin AlexanderMoskovkin modified the milestones: Sprint #9, Planned Oct 5, 2017
@miherlosev miherlosev added TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: bug The described behavior is considered as wrong (bug). labels Jul 10, 2018
@github-actions
Copy link

github-actions bot commented Dec 6, 2020

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Dec 6, 2020
@github-actions
Copy link

We're closing this issue after a prolonged period of inactivity. If it still affects you, please create a new issue with up-to-date information. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Stale An outdated issue that will be automatically closed by the Stale bot. SYSTEM: hammerhead TYPE: enhancement The accepted proposal for future implementation. TYPE: Web API support
Projects
None yet
Development

No branches or pull requests

5 participants