The global quick search can sometimes fail to take you to the searched project when clicked on
Steps to reproduce
Enter something into the global quick search at the top right of the page that will cause it to return 0 results
Clear your entered search and instead search for an actual project
Clicking the project in the search result now does nothing
What is the current bug behavior?
The quick search does not take you to the searched project when a prior search returns 0 results. You have to reload the page to make the search work again.
@changzhengliu Given that we're bringing on some FE support soon, and the impact of this and votes I'm going to drop this in to %13.0 and increase the priority/severity. Do you think we can handle it then?
I've tracked down this to a Bootstrap event handler that prevent the anchor tag to execute and start the navigation.
This handler is being added in the initialization step of the Dropdown plugin, but is re-applied when search_autocomplete.js#disable_autocomplete:411 is called, as it triggers an event via the Bootstrap Dropdown jQuery plugin which causes a re-initialization of the whole dropdown.
From that point on, the default behavior of anchors is blocked, thus no navigation occurs.
@mbergeron - Given your findings, it sounds like if we remove the search results via #213699 (closed) - this won't be an issue any longer. As that's planned for %13.0 as well, maybe that's a better path to take and then re-check this.
@phikai I agree with you, but I just found a fix to this situation and this stems from a bug in the auto-complete behavior in the front-end, so there might be other occurences of this bug in other parts of GitLab.
I think it would be worth submitting an MR for this, maybe re-assigning it to a front-end engineer to re-prioritize it while we re-focus on #213699 (closed)