Selecting one of the suggested results in the autocomplete popup with the arrow keys and hitting enter always triggers the global search instead of the selected result.

Clicking on one of the results in the popup doesn't produce any outcome.

Correction!
This works as expected and it wasn't regressed by bug 1554637.

The problem appears while working on bug 1542720, with the temp patch applied.

Confirmed that the issue appears when applying the WIP patch from https://phabricator.services.mozilla.com/D33250

I will hold on to this bug until that patch lands on m-c and do the necessary adjustments.

(In reply to Alessandro Castellani (:aleca) from comment #2)

Confirmed that the issue appears when applying the WIP patch from https://phabricator.services.mozilla.com/D33250

I will hold on to this bug until that patch lands on m-c and do the necessary adjustments.

That patch has landed, and Bug 1534455 has some noted regressions

This seems to be solved.
Can someone confirm it as well?

David, do you see this issue with current nightly?
(bug 1595884 was a mistake)

I didn't see the other bug as an error request. I am not using a Nightly at this time as too many addons were not usable when I last tried.

Here's a patch for this bug which fixes the current issue:

• Search something.
• Use the arrow keys to move through the popup results.
• Hit Enter on one of the focused results.
• The search gets triggered using what's written in the input field, ignoring the selected result in the popup.

This patch checks if a result in the popup is currently selected and forces a "popupClick" method instead of the default search based on the typed value.

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/cd095c8109ff
Fix erratic behaviour when clicking results on the glodacomplete-rich-result-popup. r=mkmelin

You should have requested backport for this for TB 72 beta. We got a complaint in bug 1490428 comment #25 for which I filed bug 1608700. Please always think of all the versions bugs need to be fixed in.