When the hoverDelay of the Menu widget is enabled the items of the Menu do not collapse properly after their initial expand.
Behavior occurs only on first expand of the items.
If the behavior isn't reproducible at initially refresh the page and try again.
Menu Items that aren't currently hovered over should collapse.
Menu Items remain expanded.
Hello again Aaron,
From the information I gathered, it looks like the bug is no longer reproduceable on newer version, it seems like it has been fixed alongside another one, thus not making an appearance on the changelog for the newer versions patch notes.
I've created a Kendo Dojo and a REPL where I've tested on the newest version, and from the testing I did, it didn't reproduce in them. Feel free to test for yourself and let us know if by some chance you managed to reproduce it.
Kind regards,
Vasko
Progress Telerik
Hello Aaron,
I understand your frustration with this particular bug and I've sent a request for more information about its status. I will get back to you within the next 24h with more information on when the team expects a fix to become available. Thank you for the patience.
Kind regards,
Vasko
Progress Telerik
Any update on this maximum-priority regression? It's been about two months since this has been reported and about four months since it has been introduced. We're stuck on version 2023.1.425 as a result of this, behind by (I think) three versions at this point with a fourth on the way, and at this rate it looks like this is going to prevent us from updating to .NET 8 when it's released.
I realize there are other priorities, and that it takes time to get issues like this figured out, fixed, and pushed through the release process. My complaint isn't that this is taking too long, my complaint is about the lack of any apparent action on this, or the lack of communication at the very least. It's hard to appreciate the new features included in the recent updates when we've been unable to take advantage of any of them, which also makes it difficult to justify our upcoming maintenance renewal. I'm not asking for an immediate fix or any promises, just an update with an idea of what to expect. Is anyone looking at this? Is there any hope for a fix by the end of the year? Next year? If not an official fix, is there any sort of workaround so we could at least stay current on updates?
Hi Aaron,
We are very sorry for the inconvenience this is causing you. It appears the bug is indeed a regression, so we've given it maximum priority (5). Based on its priority, I am expecting it to be fixed in one of the upcoming releases, but since it hasn't been planned for a specific release yet, I am afraid I cannot give you a more precise time frame.
Kind regards,
Vasko
Progress Telerik
Hi Germaine,
Thank you for the bug report, we really appreciate the feedback! Regarding the bug itself, we have added it to our issue tracker in our repository for a future fix. In addition to the report, I've given you some Telerik points, so be sure to check your account.
Regards,
Vasko
Progress Telerik
Just for clarification to avoid any confusion, we weren't able to reproduce the bug (multiple menus remaining open) in that Dojo example mentioned in "Reproduction of the problem" #1 above.
But, as mentioned in our original support ticket (here) and as you mentioned in #3 above, when using the Telerik UI for ASP.NET Core Menu TagHelper demo page the bug is consistently reproduceable. I also included screenshots of the bug from the original Support Ticket using this Menu TagHelper demo page, in case they help with identifying/troubleshooting the bug.
Also, the Kendo UI version we were using was 2023.2.606. To our knowledge, this was the version that introduced the bug.