-
Notifications
You must be signed in to change notification settings - Fork 253
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-menu: runtime error #8764
Comments
@unazko @tsanislavgatev Please have a look I debugged a bit. When the error occurs: I manually followed the DOM and found out that: Basically, when I find the "Open from local" item in the DOM and click it ($0) I can confirm that this is not the same DOM element as the one in the expression, therefore the code breaks. |
Hello @vladitasev, This issue only happens as the busy state of the The same issue isn't reproducible via the following PR: #8722 Best regards, |
Thanks for the quick fix! I've approved the PR. When the colleagues merged the change to |
Renames the busy and busyDelay properties of the ui5-menu and ui5-menu-item to loading and loadingDelay. BREAKING CHANGE: The busy and busyDelay and properties of the ui5-menu and ui5-menu-item are renamed. If you have previously used the busy, busyDelay properties: <ui5-menu header-text="My ui5-menu" busy busy-delay="100"><ui5-menu> <ui5-menu-item text="Open" icon="open-folder" busy busy-delay="100"><ui5-menu-item> now you should use loading and loadingDelay properties: <ui5-menu header-text="My ui5-menu" loading loading-delay="100"><ui5-menu> <ui5-menu-item text="Open" icon="open-folder" loading loading-delay="100"><ui5-menu-item> Fixes: #8764
Bug Description
1.Run the project locally
Click "Open Menu" -> Open -> Open Locally -> Open from C
There is a runtime error
Affected Component
No response
Expected Behaviour
No response
Isolated Example
No response
Steps to Reproduce
...
Log Output, Stack Trace or Screenshots
No response
Priority
High
UI5 Web Components Version
2.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: