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

Not able to click on buttons where AngularJS component is passed a disabled property #5147

Closed
luujam2 opened this issue May 29, 2020 · 5 comments
Assignees
Labels
AREA: client FREQUENCY: level 2 STATE: Need clarification An issue lacks information for further research. SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@luujam2
Copy link

luujam2 commented May 29, 2020

What is your Test Scenario?

We're using AngularJS (1.x), I'd like to click a button contained inside a wrapping component. The wrapping component contains a disabled property which doesn't necessarily mean the component is disabled; it's just passed to other nested components. I'm guessing when TestCafe attempts to click it, the disabled property of the AngularJS component stops the event from working.

What is the Current behavior?

Clicking on the accordion or any of its contents does nothing. However the component can still be manually toggled.

What is the Expected behavior?

Clicking on the accordion should open it. Interaction of its contents should react accordingly.

What is your web application and your TestCafe test code?

Please clone and run the test here: https://github.com/luujam2/testcafe-angularjs.
Supporting codepen: https://codepen.io/jl00161/pen/rNOXLmZ

Steps to Reproduce:

  1. Go to the aforementioned github repository
  2. Clone repository
  3. run npm i
  4. run npm test
  5. Modify the codepen to remove the disabled property
  6. run the test again

Your Environment details:

  • testcafe version: 1.8.5
  • node.js version: 10.18.1
  • command-line arguments:
  • browser name and version: Chrome 83
  • platform and version: MacOS 10.14
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label May 29, 2020
@luujam2 luujam2 changed the title Not able to click on buttons where AngularJS a component is passed a disabled property Not able to click on buttons where AngularJS component is passed a disabled property May 29, 2020
@AlexKamaev
Copy link
Contributor

Thank you for your input. I was able to reproduce the issue.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jun 1, 2020
@AlexKamaev AlexKamaev added TYPE: bug The described behavior is considered as wrong (bug). SYSTEM: automations AREA: client labels Jun 1, 2020
@AlexKamaev AlexKamaev added this to the Planned milestone Jun 1, 2020
@LuudJanssen
Copy link

LuudJanssen commented Jun 1, 2020

I'm also running into this issue. I found that this happens to me from version 1.8.3 onward.

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jun 1, 2020
@AlexSkorkin AlexSkorkin removed the STATE: Need response An issue that requires a response or attention from the team. label Jun 2, 2020
@AndreyBelym
Copy link
Contributor

AndreyBelym commented Oct 6, 2021

Probably related to #5240

@miherlosev
Copy link
Collaborator

miherlosev commented Jan 11, 2022

Hi @luujam2

A similar issue was fixed.
I cannot check the shared example, because I cannot get through the 'I am human' check using TestCafe.
Could you please modify your example so that we can download it and run it locally?

@miherlosev miherlosev added the STATE: Need clarification An issue lacks information for further research. label Jan 11, 2022
@no-response
Copy link

no-response bot commented Jan 21, 2022

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.

@no-response no-response bot closed this as completed Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AREA: client FREQUENCY: level 2 STATE: Need clarification An issue lacks information for further research. SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

6 participants