keybase / keybase/keybase-issues
Website search - results list issues
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
System
Crunchbang's "Iceweasel" v24.8.1 (Firefox), Crunchbang 11 with not quite the latest updates at time of writing (uname -a: Linux abort 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux). Four-core AMD Athlon II @ 3.8GHz with 16GB RAM.
Description
If you type "a" or a similarly broad search term into the Search box in the website header, I will get a drop-down with a bounded list of results (20). If your browser window is not "tall" enough to display the 20 matches, there is no way to scroll the list. Scrollbars and scrollwheel actions move the page behand the results list. You can scroll through the drop-down list using arrow keys, which only shows the result/match term in search box - not including any of the additional identity info from the listing, which might be important in determining if this is a match you wanted.
There is no way to request a "normal" page of results, or to request the next set of 20 matches.
Sometimes entering "e" followed immediately by Return will bring up the list of matches - other times it will bring up the first autocompleted match. This may be due to browser performance issues not showing the autocompletion between "e" and Return (e.g. a 4.1GB Firefox process (3GB resident) is slow), but the behavior should be consistent for least user surprise.
Workaround
No workaround at this time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the website header search with broad terms such as "a" or "e", including a short browser window and pressing Return quickly. Review the search dropdown behavior and make scrolling, pagination or a normal results page, and autocomplete-versus-submit behavior consistent. Done means users can reach all matches and reliably submit the intended search.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, search, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100