-
Notifications
You must be signed in to change notification settings - Fork 672
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
Firefox waits for an element without necessity #2080
Comments
I'm also experiencing the exact same thing in both Firefox and IE 11. Chrome (and headless Chrome) both work fine. |
Can confirm this behavior |
same issue in chrome |
Hi @adback03 @berrutti @arenddeboer! The fix is released in |
Hello, please, can you confirm this issue is fixed? I'm running testcafe v 0.22.0 and the issue is occuring for me everytime I use selectText action (on both Windows with Chrome, and remote device - iPad with Safari). |
@AlisarDius |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow. |
…evExpress#2760) * Should find element with not-integer offset (closes DevExpress#2080) * more tests * remove tests * remove excess element
Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
During the test, Firefox waits for some element to appear for no reason.
What is the expected behavior?
Firefox does not wait for an element during the specified test.
How would you reproduce the current behavior (if this is a bug)?
Run the specified test. Firefox types text into an input, then waits for something for the entire timeout period and then continues the test.
Provide the test code and the tested page URL (if applicable)
Tested page URL: http://devexpress.github.io/testcafe/example/
Test code
https://github.com/DevExpress/testcafe/blob/master/examples/basic/test.js#L49
Specify your
The text was updated successfully, but these errors were encountered: