@ovasileva, this task is ready and just needs scheduling.

I dug into this a bit today, and this bug is interesting. It's not a problem with the CSS or positioning of the search suggestions, but it's tied to how Android handles blur events.

Essentially, when an input looses focus, it should emit a blur event, and then a click event on whatever was clicked. This works as expected when both the input and the clicked element are in the viewport, but things get funny when they're not.

When an input is scrolled past the viewport while it has focus, and then a blur event is triggered, the browser scrolls back up to make the input visible, instead of emitting the click event on the clicked element.

This behaviour is consistent when clicking on anything on the page, not just the search suggestions, and it happens on Chrome and Samsung Browser (I think both Blink based) Firefox on Android emits the click events correctly.

I made a codepen to reproduce this behaviour https://codepen.io/j4n/full/vwqYWa when tapping the input, then scrolling down and clicking a link, the link isn't followed, instead the browser scrolls back up to the input. One can also try scrolling past the search suggestions on the portal page and clicking on a project link, the browser will scroll back up as well.

I was about to decline this ticket because the bug seems to be an Android Chrome issue, but then I thought "how does the mobile wikipedia site handle this issue?" and I discovered that the mobile site triggers a blur event when a user scrolls down. That way, the browser doesn't scroll back up when something is clicked. The same approach can be applied here.

Change 525044 had a related patch set uploaded (by Jdrewniak; owner: Jdrewniak):
[wikimedia/portals@master] Fix search suggestion clicking on Android Chrome.

https://gerrit.wikimedia.org/r/525044

Change 525044 merged by jenkins-bot:
[wikimedia/portals@master] Fix search suggestion clicking on Android Chrome.

https://gerrit.wikimedia.org/r/525044