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

Ember elements cause Uncaught TypeError #966

Closed
ClaytonAstrom opened this issue Nov 15, 2016 · 7 comments
Closed

Ember elements cause Uncaught TypeError #966

ClaytonAstrom opened this issue Nov 15, 2016 · 7 comments
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

@ClaytonAstrom
Copy link

ClaytonAstrom commented Nov 15, 2016

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 filtering

What 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

"use strict";

fixture("Text Field")
    .page("https://www.twitch.tv/directory");

test("Search for a test", async t => {
    await t.typeText(() => document.querySelector("#gameselector_input"), "Test");
    //I believe no matter what selector/function you put here, the entire page will fail to load

});

Specify your

  • operating system: Windows 7
  • testcafe version: 0.10.0
  • node.js version: 6.9.1
  • Ember versions: 1.13 and 2.4.4
@georgiy-abbasov
Copy link
Contributor

Hi @ClaytonAstrom.

Thank you for the report. We have reproduced the problem and we are working on it.

@georgiy-abbasov georgiy-abbasov self-assigned this Nov 16, 2016
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Nov 16, 2016
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #2 milestone Nov 16, 2016
@georgiy-abbasov
Copy link
Contributor

Waiting for solving DevExpress/testcafe-hammerhead#942

@georgiy-abbasov
Copy link
Contributor

@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 npm install testcafe@alpha.

@ClaytonAstrom
Copy link
Author

Looks good from my end, thanks @georgiy-abbasov !

@georgiy-abbasov
Copy link
Contributor

@ClaytonAstrom, it's great news! Can we close the issue ?

@ClaytonAstrom
Copy link
Author

Done!

@lock
Copy link

lock bot commented Mar 29, 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 An issue has been automatically locked by the Lock bot. label Mar 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 2019
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

No branches or pull requests

3 participants