-
Notifications
You must be signed in to change notification settings - Fork 273
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
[Menu & MenuItem | 1.14.0]: The Dynamic Menu is not working on the second sub-level #7391
Comments
Hello @SAP/ui5-webcomponents-topic-b, This issue is for us. Best regards, |
Issue: - The sub-menu busy state and dynamically loaded items weren't proeprly updated. Fixes: SAP#7391
Hi @unazko , Is there any update on this? |
Hi @rv97, Apologies for the late reply. We've got stuck with merging the previously related PR. Best regards, |
- The ui5-menu elements used for sub-menus are created only once and are being reused afterwards. They are no longer destroyed on close. This contributes to lowering the count of the slow DOM manipulation operations. - There is now no differentiation between mobile and desktop device in regards to the display mechanism. In both cases we rely on the template to do the job as the components used for composition like ui5-list and ui5-responsive-popover do comply with the device. Fixes: SAP#7767 Fixes: SAP#7423 Fixes: SAP#6761 Related to: SAP#7391
Hello @rv97, I've managed to fully test the provided sample and unfortunately the previously linked PR's aren't going to fix this issue: There is a workaround at least. We're going to continue debugging this behavior. Best regards, |
Hi @unazko, I'm from @rv97' team working on this issue. The workaround you proposed is not working in our case. We have a complex reusable component which is used to render all the menus across the entire application. Introducing the workaround in our application brings in a lot of code refactoring and unnecessary errors. Hence, we request the UI5 Web Components Team to check if it is possible to fix this issue in the Thanks & Regards, |
Hi @rv97 & @shubhamnazare, We're actively addressing your concern and will update you shortly. Regards, |
Hi @DMihaylova , Thanks for the update. Regards, |
The `ui5-menu-item` now extends `ListItem` abstract class and it will be represented directly as a list item in the DOM. The application developers could now add custom styles and attach native event handlers to the `ui5-menu-item` as it is no longer an abstract class, but a physical component: ```html <ui5-menu-item id="exitItem" text="Exit" style="border: 2px solid teal" icon="journey-arrive"></ui5-menu-item> ``` ```ts document.getElementById("exitItem").addEventListener("focusin", () => { ... }) ``` Related to: #8461 Related to: #7391
Thanks @unazko. Please let us know once you have finalized the version this fix would be available from. Thanks, |
Hi Vignesh R, This behavior will be fixed with webc v2 currently. We'll be working on a transport as a separate fix for 1.24.x releases. You could perform internal testing with the release candidate (2.0.0-rc.4). There is also information about the incoming releases down on the following page: https://github.com/SAP/ui5-webcomponents/projects?type=classic We expect to have an official release containing the working behavior at the end of June. Best regards, |
Hi @unazko, Since we are yet to move to v2, we are expecting the fix in one of the V 1.x. Appreciate if you can let us know by when we can expect the fix. reagrds |
Hi @unazko Can you please comment on this as we need an urgent fix for this issue? |
Hi @Abanindra, I've referenced a PR, which will fix this issue for Best regards, |
Hi @Abanindra, The fix is done and it is transported into Best regards, |
Thank you @unazko for the update. |
Thanks @unazko ! |
Hi @unazko I was validating the fix with the above codesandbox example and unfortunately the issue is still reproducible. The versions I used were - Could you please validate from your side and confirm the same if possible. Thanks a lot! |
Hi @unazko As I mentioned this issue is still reproducible in 'ui5/webcomponents: 1.24.8' and 'ui5/webcomponents-react: 1.29.6'. Could you please validate and let me know what are the next steps? |
Hi @shubhamnazare, The previous sample from the codesandbox doesn't load for me. The "New file" menu item has sub-menu and afterwards we have second level of nested sub-menus. Could you please test at your side and edit the sample if necessary so the issue is reproducible? |
Hi @unazko , I opened the sandbox link which you had mentioned. I am still able to reproduce the issue. Steps: You can see it is stuck at the loading indicator forever until i go back one level and open it again. |
Hi @rv97, Thanks for the reproduction steps. |
Hi @rv97, @shubhamnazare, @Abanindra, The issue is now fixed via the related change in 1.24.10 patch, which was just released. |
Bug Description
When the main menu has two levels of sub-menu where the second level sub-menu should be rendered dynamically, then the loading indicator is stuck and does not render the content automatically. We need to go one level back and then open the sub-menu to show the rendered content.
The same works in the case of the first-level sub-menu.
Affected Component
Menu, MenuItem
Expected Behaviour
How many ever sub-levels are there, the busy indicator should be gone automatically and render the content.
Isolated Example
https://codesandbox.io/s/prod-bird-mjtv35?file=/src/App.js
Steps to Reproduce
...
You can observe that the sub-menu inside a sub-menu does not render the content automatically.
Log Output, Stack Trace or Screenshots
No response
Priority
High
UI5 Web Components Version
1.14.0
Browser
Chrome
Operating System
MacOS
Additional Context
No response
Organization
SAP Labs
Declaration
The text was updated successfully, but these errors were encountered: