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 proxing Function.prototype.toString when it was overriden in customer script #999

Closed
helen-dikareva opened this issue Dec 19, 2016 · 4 comments
Assignees
Labels
Milestone

Comments

@helen-dikareva
Copy link
Collaborator

Only in Chrome on iPad.

Page from SC Infinite page T461403:
https://staging.lostmy.name/personalized-products/lost-my-name-book/preview?customisation_locale=en-GB&gender=boy&name=Chris&phototype=type-iii

Reproduced with hammerhead playground, sometimes chrome closes during opening this page in playground.

@miherlosev
Copy link
Contributor

I'm working on this

@miherlosev
Copy link
Contributor

miherlosev commented Dec 20, 2016

I think I reproduced the issue on desktop version (55.0.2883.87 m )
see video

@helen-dikareva
Copy link
Collaborator Author

Cool, it's event better

@miherlosev miherlosev changed the title Infinite page loading Wrong proxing Function.prototype.toString that was overriden in customer script Dec 23, 2016
LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Dec 26, 2016
@miherlosev miherlosev changed the title Wrong proxing Function.prototype.toString that was overriden in customer script Wrong proxing Function.prototype.toString when it was overriden in customer script Jan 12, 2017
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
@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
Projects
None yet
Development

No branches or pull requests

3 participants