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

Hammerhead throw an error, when "xhr.onreadystatechange" property is broken. #1012

Closed
georgiy-abbasov opened this issue Jan 13, 2017 · 2 comments
Assignees
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug

Comments

@georgiy-abbasov
Copy link
Contributor

We have faced with situation, when getter and setter of property xhr.onreadystatechange are broken.
In cases without testcafe, it doesn't lead to a problem, when isn't using. But when we try to use testcafe, it tries to check this property here. It leads to problem, regardless of is used whether xhr.onreadystatechange on the original page or not.

Example, where another frameworks try to use this property

@georgiy-abbasov georgiy-abbasov self-assigned this Jan 13, 2017
@miherlosev miherlosev added this to the Planned milestone May 16, 2017
@miherlosev miherlosev modified the milestones: Planned, Sprint #11 May 11, 2018
@LavrovArtem LavrovArtem modified the milestones: Sprint #11, Sprint #12 May 14, 2018
@LavrovArtem
Copy link
Contributor

fixed in #1287

@LavrovArtem LavrovArtem removed this from the Sprint #12 milestone May 30, 2018
@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 STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

3 participants