1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Design Issue Quick Search bug

Discussion in 'Resolved Bug Reports' started by batpool52!, Jan 5, 2016.

  1. batpool52!

    batpool52! Well-Known Member

    Steps to reproduce
    1. Click on "Search" which below visitor tab
    2. Then hover on the little arrow button
    3. A menu should appear
    4. Click on "Useful Searches"
    5. Click somewhere release on the page
    6. "Useful Searches" overlay stays in the page even though the search block is gone
    [​IMG]
     
    erich37 likes this.
  2. Mike

    Mike XenForo Developer Staff Member

    Specifically, it's clicking within the menu that appears. Clicking elsewhere on the page will close both. I'm not sure if there's an easy fix to this though.
     
  3. Mike

    Mike XenForo Developer Staff Member

    I'm going to have to call this a design issue I think. The useful searches menu is separate from the search popup in terms of the DOM, so there isn't really a particularly good way to connect the two to indicate the search popup should stay when you click the "child" menu.
     
  4. Daniel Hood

    Daniel Hood Well-Known Member

    Just a suggestion:

    I fixed it by editing the dom in my developer console. If you bring the menu into the search form element and adjust the style attribute to
    Code:
    right: 20px; display: block; visibility: visible;/* left: 1212.5px; */top: 275px;right: 5px;
    it works properly. I haven't looked into how much javascript would have to be changed though. Might not be feasible.
     
  5. Mike

    Mike XenForo Developer Staff Member

    Just in case you're not aware, the menu system doesn't work like that. The JS moves them at the end of the DOM and then positions them. Not doing this creates potential z-index issues and--more significantly--worksaround overflow:hidden/auto usage.
     
    Daniel Hood likes this.
  6. Daniel Hood

    Daniel Hood Well-Known Member

    Kind of figured as much. Thanks for explaining though.

     

Share This Page