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

Wrong behaviour for window.fetch request called without parameters #939

Closed
miherlosev opened this issue Nov 14, 2016 · 2 comments
Closed
Assignees
Labels
AREA: client !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@miherlosev
Copy link
Contributor

Found in http://bxt-to-wc-weu-tst.azurewebsites.net/ site.

Without proxing:

var result = window.fetch();
result:
[[PromiseStatus]]:"rejected"
[[PromiseValue]]:TypeError: Failed to execute 'fetch' on 'Window': 1 argument required, but only 0 present. at eval (eval at evaluate (:117:21), <anonymous>:1:13) at http://localhost:3000/:16:5

With proxing:

var result = window.fetch();
result:
[[PromiseStatus]]:"pending"
[[PromiseValue]]:undefined
@miherlosev
Copy link
Contributor Author

I'm working on this

miherlosev pushed a commit to miherlosev/testcafe-hammerhead that referenced this issue Nov 16, 2016
miherlosev pushed a commit to miherlosev/testcafe-hammerhead that referenced this issue Nov 16, 2016
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
…rs' (close DevExpress#939) (DevExpress#946)

* fix 'Wrong behaviour for window.fetch request called without parameters' (close DevExpress#939)

* add new line
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

1 participant