-
Notifications
You must be signed in to change notification settings - Fork 275
[Panel]: Raise error sometimes #11556
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
Screen.Recording.2025-05-21.at.10.31.16.mov |
I wasn't able to reproduce this error. Could you please add an isolated example, preferably by using this StackBlitz template. Please also include the version of the browser and the OS where this error is occurring in. |
Hi @Lukas742 This is not easy to reproduce, as I mention in the content, you need to click the button randomly and repetitively. Sometimes it fails at first time, sometimes it never fails. macos version: 15.4.1 |
@wilson-xu-sap I clicked multiple times, with different intervals, but no error is thrown for me. (Tested in Chrome and Safari) Edit: I got it. When clicking close to the border of the button, the error is thrown. |
@wilson-xu-sap I'll forward this issue to the ui5-webcomponents repo, as the component is developed there. Hi Colleagues, when clicking close to the border of the button that is rendered if a custom 2025-05-21_08-45-16.mp4It seems that a |
@Lukas742 Thanks for your carefulness and patience! |
Hello @SAP/ui5-webcomponents-topic-b, Could you please take a look at that issue? I think it's related to change introduced with: #11318 The issue is reproducible when the click occurs over the border of the component. Regards, |
Describe the bug
Isolated Example
https://sap.github.io/ui5-webcomponents-react/v2/?path=/story/layouts-floorplans-panel--with-custom-header
Reproduction steps
Randomly click the collapse button
Expected Behaviour
No response
Screenshots or Videos
No response
UI5 Web Components for React Version
2.10
UI5 Web Components Version
2.10
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: