@nickykrause commented on Tue May 16 2017
While testing this script, when one user entered a person's name into the site-wide search and then tried to select search individual contributions from: [name] in the typeahead, nothing happened. It seemed like the button was not responding.
I am able to replicate this issue on my machine by searching for a name -- nothing happens when I try to click search individual contributions...:

Specifically, it seems that if my mouse is over the text, then it doesn't work. If I move the mouse so that it is still within the button but NOT over the text, then the button is clickable.
@nickykrause commented on Mon May 22 2017
FYI: This came up again in testing last Friday
@jenniferthibault commented on Thu Jul 13 2017
This gets me all the time. :shakes-fist:
@nickykrause commented on Thu Jul 20 2017
This doesn't seem to be an issue anymore. @noahmanger -- was this actively fixed at some point, as a part of some recent release?
Is this something we still need to address?
I think so. There still seems like there are barriers to usability here.
When you want to select something from the "search individual contributor" field in the typeahead, and it's in the first position, it seems like only the top 1/3 of the field is an active button/link, which makes it really frustratingly hard to click that option. Screencapture:

I think this is something we can try to address in the normal course of business during this PI.
Noting for future github archeology:
This issue has not been addressed and was closed as part of a batch of issues that have been iceboxed for an extended period of time. The problems described above still exist as of the point this issue was closed.
Thanks, @jenniferthibault . I'm going to put this into our backlog.
This problem still exists (6/11/2019)
The main site menu was in a layer higher than the search results so the mouse events across that range went to the menu bar instead of to the drop-down. This should be fixed by PR #3250