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

Firefox waits for an element without necessity #2080

Closed
VasilyStrelyaev opened this issue Jan 29, 2018 · 7 comments · May be fixed by marcusrc/testcafe#1
Closed

Firefox waits for an element without necessity #2080

VasilyStrelyaev opened this issue Jan 29, 2018 · 7 comments · May be fixed by marcusrc/testcafe#1
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@VasilyStrelyaev
Copy link
Contributor

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

  • operating system: Windows 10
  • testcafe version: 0.18.7-dev20180117
  • node.js version: 9.2.0
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Feb 5, 2018
@adback03
Copy link

I'm also experiencing the exact same thing in both Firefox and IE 11. Chrome (and headless Chrome) both work fine.

@miherlosev miherlosev added this to the Planned milestone May 7, 2018
@berrutti
Copy link

Can confirm this behavior

@arenddeboer
Copy link

same issue in chrome

@AndreyBelym
Copy link
Contributor

Hi @adback03 @berrutti @arenddeboer! The fix is released in [email protected], you can install it with npm i testcafe@latest and try it on your machine.

@AlisarDius
Copy link

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).
I even tried npm i testcafe@latest - installed TestCafe v 0.23.2 but without any change.

@AlexSkorkin
Copy link
Collaborator

@AlisarDius  
Yes, we confirm that this issue has been fixed. If you think that this issue still exists, please submit a new issue with your sample test, your webpage URL and all steps we need to perform, so we can examine it. Thank you in advance.

@lock
Copy link

lock bot commented Mar 27, 2019

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.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 27, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
…evExpress#2760)

* Should find element with not-integer offset (closes DevExpress#2080)

* more tests

* remove tests

* remove excess element
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants