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

TestCafe shows <select> options when the dropdown element is disabled #5616

Closed
stefanschenk opened this issue Oct 8, 2020 · 1 comment · Fixed by #6776
Closed

TestCafe shows <select> options when the dropdown element is disabled #5616

stefanschenk opened this issue Oct 8, 2020 · 1 comment · Fixed by #6776
Assignees
Labels
AREA: client FREQUENCY: level 1 TYPE: bug The described behavior is considered as wrong (bug).

Comments

@stefanschenk
Copy link
Contributor

stefanschenk commented Oct 8, 2020

Not much more to this issue. TestCafe will show the options of dropdown box when this element is disabled in the dom. Solution: respect disabled state of element.

Your Environment details:

  • testcafe version: 1.8.6
  • node.js version: v12.16.1
  • browser name and version: Chrome 81.0.4044.0
  • platform and version: macOS 10.15.7

Select element with status disabled
image

Dropdown options are show even if the select element is disabled
image

@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 8, 2020
@Ogurecher
Copy link
Contributor

@stefanschenk

Thank you for your report. I've reproduced the issue and we'll update this thread once it's fixed.
For the team: see DevExpress/testcafe-hammerhead#2346 - this might be a bug in this PR's implementation.

@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 12, 2020
@Ogurecher Ogurecher added AREA: client FREQUENCY: level 1 STATE: Need research TYPE: bug The described behavior is considered as wrong (bug). labels Oct 12, 2020
@Aleksey28 Aleksey28 self-assigned this Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AREA: client FREQUENCY: level 1 TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants