Good day All,
I came across a weird issue after I recently upgraded to Volume 13.1 of the ASP.NET controls. (v13.1.20131.2045)
We are using an ASP.NET WebDataMenu for our web app to navigate to the different sections in our application.
We hide/disable menus depending on the user's access level.
My own user with which I log in, has access to all menu's, so I didn't see the problem at first.
I tested with a lower level user, and noticed after I logged in (and the menu is set), there is a delay on the application and IE reports a long-running script error, and the F12 developer tools report a stack overflow error.
I started testing by disabling menu activation code, etc, until I hit the first menu that is disabled.
I started Googling and found a thread here speaking of issues with the WebDataMenu in tables (for v10.1), so I changed the EnableScrolling property to "False", and VOILA! Long running script error is gone!
I tested on an older branch with the same user using the v12.2 (12.2.20122.2054) controls, and the error does not occur there.
Can you guys @ Infragistics have a look and maybe log this as a bug?
Thanks!!
Hello Eduard ,
I’m just following up to see if you’ve been able to resolve your issue. If you have any questions or concerns or if you need further assistance please let me know.
Best Regards,
Maya Kirova
Developer Support Engineer
Infragistics, Inc.
http://ko.infragistics.com/support
I tested this using the exact same version 13.1.20131.2069 however I have not been able to reproduce this.
Could you let me know the following things:
Are there any specific steps needed to reproduce this?
I tried logging in and out a few times but I didn’t notice any delay or long running script error.
Could you check whether the document and browser mode in your browser are both set to IE9? Are they perhaps set to an older version?
I’m looking forward to your reply.
Developer Support Engineer II
Hello Maya,
Yes, I've resolved it by setting the EnableScrolling to "False" for the menu, which was a suggestion I got from the Infragistics forums indirectly.
This was something that happened after we upgraded our solution to Volume 13.1, on our old v12.2 branches it works fine.
Thank you for the sample.
I’ve attached a video for your reference.