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

Element returns aria-hidden=true property only during TestCafe script. #8064

Closed
harry7771 opened this issue Oct 30, 2023 · 1 comment
Closed
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@harry7771
Copy link

What is your Scenario?

Click a dropdown in my company's Workday app via TC script.

What is the Current behavior?

A 'button' element returns a property of 'display: none' or aria-hidden=true during a run of the TC script, but the element does not return those properties when the same workflow is run manually. My script is therefore unable to click the screen element.
Here is the TC error:
The action target (...) is invisible.
It descends from an element that has the 'display: none' property (

...
).

What is the Expected behavior?

I would expect TC to return the same element properties during the automated script as when it is run manually.

What is the public URL of the test page? (attach your complete example)

Unfortunately there is no public access to this site.

What is your TestCafe test code?

const editStatementDropdown = Selector('div[title="Statements"]').find('button[title="Edit"]');

Your complete configuration file

no config file in use

Your complete test report

A 'button' element returns a property of 'display: none' or aria-hidden=true during a run of the TC script, but the element does not return those properties when the same workflow is run manually. My script is therefore unable to click the screen element.
Here is the TC error:
The action target (...) is invisible.
It descends from an element that has the 'display: none' property (

...
).

Screenshots

image

Steps to Reproduce

TestCafe version

3.1.0

Node.js version

18.17.1

Command-line arguments

testcafe chrome demo.test.js -e

Browser name(s) and version(s)

latest of Chrome and Firefox

Platform(s) and version(s)

No response

Other

No response

@harry7771 harry7771 added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 30, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 30, 2023
@harry7771
Copy link
Author

Fixed!
Simply added the following to the existing selector: .filterVisible()

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

1 participant