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

[ui5-switch]: breaks testing tools #10773

Open
1 task done
nnaydenow opened this issue Feb 5, 2025 · 0 comments · May be fixed by #10798
Open
1 task done

[ui5-switch]: breaks testing tools #10773

nnaydenow opened this issue Feb 5, 2025 · 0 comments · May be fixed by #10798
Assignees
Labels
bug This issue is a bug in the code TOPIC B

Comments

@nnaydenow
Copy link
Contributor

nnaydenow commented Feb 5, 2025

Bug Description

Recent change introduced with #10588 breaks testing tools like Cypress because they check the custom element for specific styles (the ui5-switch adds pointer-events: none).

Here is an example for some of the rules https://docs.cypress.io/app/core-concepts/interacting-with-elements#An-element-is-considered-hidden-if

Revise and change that

Affected Component

ui5-switch

Expected Behaviour

No response

Isolated Example

No response

Steps to Reproduce

...

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

nightly

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

No response

Declaration

  • I’m not disclosing any internal or sensitive information.
@nnaydenow nnaydenow added bug This issue is a bug in the code TOPIC B labels Feb 5, 2025
@hinzzx hinzzx self-assigned this Feb 5, 2025
@hinzzx hinzzx moved this from New Issues to In Progress in Maintenance - Topic B Feb 7, 2025
@hinzzx hinzzx linked a pull request Feb 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug in the code TOPIC B
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants