Inconsistent enter behavior

[bcye]

When searching, it seems the Enter button has a different behaviour for different scenarios (especially when typing quickly):

1. When the search page hasn't yet settled (or even loaded), the enter key (while typing, the search input focused) seems to do a browser navigation to search
2. In the card view, after the results have completely loaded, pressing Enter causes a navigation to the exact match, if that exists
3. In the table view, it causes the search page to be reloaded (when the text input is highlighted)

It seems that until the search results have settled the keydown propagates to the still highlighted search input whose behaviour seems to be from 1) and 3) to navigate to the search input.

I'd suggest that if the results have not settled or if the search input handles the key down, the page assumes that it will be an exact match and navigates to /search-term. The main problem with the current behavior is that if you type quickly and press enter, the site possibly first reloads, then you wait a second, press it again and get to the exact match.

[alexdln]

@bcye hi :)

Could you please check it now? I've fixed the search behavior, and these issues probably as well.

If the page isn't loaded or JavaScript is disabled, I think first is the correct behavior. Unfortunately I don't remember about the 2nd scenario. And the reloading issue when switching between pages or when already on a page has definitely been fixed.

#733

[bcye]

Hey @alexdln, yeah search seems much more stable, thank you :)

I think it would be useful to have a way to directly go to the package typed in and not have to wait for the search to load to proceed. I'm thinking the best way would be to just have the enter key when focused on the search bar do this -- will do a pr.