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

The XhrSandbox.openNativeXhr method can return xhr with an overriden 'setRequestHeader' function #1252

Closed
LavrovArtem opened this issue Aug 1, 2017 · 2 comments
Assignees
Labels
AREA: client !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@LavrovArtem
Copy link
Contributor

@LavrovArtem
Copy link
Contributor Author

I'm working on this

LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Aug 2, 2017
@miherlosev miherlosev changed the title The XhrSandbox.openNativeXhr function calls non native the xhr.setRequestHeader function The XhrSandbox.openNativeXhr method can return xhr with an overriden 'setRequestHeader' function Aug 16, 2017
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
…etRequestHeader function` (close DevExpress#1252) (DevExpress#1254)

* fix `The XhrSandbox.openNativeXhr function calls non native the xhr.setRequestHeader function` (close DevExpress#1252)

* fix test

* test refactoring
@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