-
Notifications
You must be signed in to change notification settings - Fork 103
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
[SAP][Analytical Table]: OnRowSelect, OnRowClick event fired when space is pressed not on keyUp #4388
Comments
You mean the other way around, right? Is there a guideline for this? And if so, could you send it to me? |
@Lukas742 SAP internal team has done accessibility testing for our product and they have reported this issue also for Button component, onClick is fired when key is released. so I think both the components should have same behaviour |
unfortunately, we haven't implemented this behavior in any of our components, and especially for the AnalyticalTable, this change could be considered breaking, as it's possible to hook into this behavior and change it on the developer side. That's why we decided to add this to our roadmap for the 2.0 release, but we can't implement it yet. |
🎉 This issue has been resolved in version v2.0.0-rc.0 🎉 The release is available on v2.0.0-rc.0 Your semantic-release bot 📦🚀 |
Describe the bug
click event should be fired on keyDown not onKeyUp
analytical table onRowSelect and onRowClick is fired when space is pressed
Isolated Example
Can be reproduced in https://sap.github.io/ui5-webcomponents-react/?path=/docs/data-display-analyticaltable--docs
Reproduction steps
Issue:- onRowSelect is triggered and row gets selected
Expected Behaviour
Expected behaviour:- it should be triggered when space key is released.
Note:- This issue is raised by SAP internal Accessbility testing team BCP ticket n0:- 2370008332
Screenshots or Videos
No response
UI5 Web Components for React Version
1.10.3
UI5 Web Components Version
1.10.3
Browser
Chrome
Operating System
macos
Additional Context
No response
Relevant log output
No response
Declaration
The text was updated successfully, but these errors were encountered: