RadMenu z-index stops updating after a while

2 posts, 0 answers
  1. Eric Garrison
    Eric Garrison avatar
    4 posts
    Member since:
    Aug 2007

    Posted 22 Jan 2013 Link to this post

    I have veritcal radmenu containing root items of different lengths and sub menus under the root items. When the page first opens the sub menus correctly show on top of the root items when expanded. After moving the mouse back and forth expanding the root items eventually the sub menus are showing behind some of the root menus. When I inspect the elements I can see that normally the root items swap between a 7000 and 8000 z-index depending if the sub menu is expanded or not. When the root items start to show through the sub menus I can see that the z-index for the root item showing through the sub menu is stuck at 8000. It is as if a javascript stopped working correctly. This is happening in Chrome, Safari and Firefox so far.

    Any ideas on how to get this to work? I have attached an image of the issue.
  2. Boyan Dimitrov
    Admin
    Boyan Dimitrov avatar
    1746 posts

    Posted 25 Jan 2013 Link to this post

    Hello,

    I would like to clarify a couple of things about your scenario. An expected behavior is applying a higher z-index value to the currently expanded menu item in order to get that item to top position. In this case if the currently expanded menu item is overlapping any other item might cause such appearance behavior showed in the provided screenshot.

    An easy and convenient approach to avoid this issue would be to use one RadMenu instance and add hierarchical structure  of all items instead of using a single RadMenu for each root item. This way you can avoid that overlapping issue and any conflict consequences  that might occur.


    Regards,
    Boyan Dimitrov
    the Telerik team
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top