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.

Sign up for GitHub

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

Jump to bottom

Improve Electron support in TestCafe #4208

Closed
1 task
AndreyBelym opened this issue Aug 28, 2019 · 3 comments
Closed
1 task

Improve Electron support in TestCafe #4208

AndreyBelym opened this issue Aug 28, 2019 · 3 comments
Labels
COMPLEXITY: hard STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.

Comments

@AndreyBelym
Copy link
Contributor

AndreyBelym commented Aug 28, 2019 •
edited

  • (From Electron app: cannot get a file via XMLHttpRequest (non-asar / asar) testcafe-hammerhead#2105) TestCafe can't execute some XHR requests to file: origins due to Content Security Policy problems. When an app is loaded without TestCafe, app's page origin is also file:, so all file: XHR requests are considered same-domain in Electron. When TestCafe loads a tested page from a file: origin, it tries to use Chrome's content policies that consider each different file path as a different origin.
@AndreyBelym AndreyBelym mentioned this issue Aug 28, 2019
Closed
@miherlosev miherlosev added TYPE: enhancement The accepted proposal for future implementation. COMPLEXITY: hard labels Aug 28, 2019
@AndreyBelym
Copy link
Contributor Author

TODO: #4701

@github-actions
Copy link

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 Jan 29, 2021
@github-actions
Copy link

github-actions bot commented Feb 9, 2021

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

@github-actions github-actions bot closed this as completed Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
COMPLEXITY: hard STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miherlosev @AndreyBelym