-
Notifications
You must be signed in to change notification settings - Fork 273
[SF][SplitButton]: [SplitButton requires two presses of Enter or Space to be activated] #11115
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
Comments
Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository. |
Hello @SAP/ui5-webcomponents-topic-b, The issue is reproducible in the provided snippix. |
Hello @tandan0813 , By using Chrome, on Windows machine, I am not able to reproduce the issue. Could you please confirm that I understood correctly the reproduction steps and the issue itself ?
Following those steps on your end requires to press Space or Enter two times in order to activate the Button's main action ? Is that correct ? Here is a video of me trying to reproduce the issue. 2025-03-18_15-17-09.mp4Best Regards, |
Hi @tandan0813, After a discussion with @nnaydenow we managed to reproduce the issue. The issue is actually that an event is not being thrown the first time we focus out of the split button and then focus in again using Shift + Tab combination. We're working on a fix. Best Regards, |
Describe the bug
Please see the isolated example: https://stackblitz.com/edit/github-2or1936m?file=src%2FApp.tsx
In tab navigation, the button can be activated once by pressing Enter or Space. However, when using Shift + Tab, the split button requires two presses of Enter or Space to be activated.
Isolated Example
https://stackblitz.com/edit/github-2or1936m?file=src%2FApp.tsx
Reproduction steps
Expected Behaviour
No response
Screenshots or Videos
No response
UI5 Web Components for React Version
2.8.0
UI5 Web Components Version
2.8.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: