-
Notifications
You must be signed in to change notification settings - Fork 674
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
Ember elements cause Uncaught TypeError #966
Comments
Hi @ClaytonAstrom. Thank you for the report. We have reproduced the problem and we are working on it. |
Waiting for solving DevExpress/testcafe-hammerhead#942 |
@ClaytonAstrom, we have fixed this in our new version (it's with alpha tag now). Please check whether the fix works with your site. To install fix, run |
Looks good from my end, thanks @georgiy-abbasov ! |
@ClaytonAstrom, it's great news! Can we close the issue ? |
Done! |
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. |
Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
Uncaught TypeError: e.getAttribute is not a function
We're unable to interact with Ember text input fields that are rendered through Ember. We believe it's due to Ember Objects making their way through TestCafe DOM Elements filteringWhat is the expected behavior?
The test is able to interact with Ember elements
How would you reproduce the current behavior (if this is a bug)?
Running similar tests against sites that use Ember textfields
Provide the test code and the tested page URL (if applicable)
Tested page URL: https://www.twitch.tv/directory
Test code
Specify your
The text was updated successfully, but these errors were encountered: