Search doesn't work if you type too fast
Project Member Reported by email@example.com, Mar 29 2018
Affected Version: 475.0 What steps will reproduce the problem? 1. Type [file:] in the search box 2. Wait for autocomplete popup to appear 3. Type [x] <Enter> as close together as possible, such that Enter is pressed before the autocomplete popup disappears. What is the expected output? Search for [file:x] What do you see instead? Search for [file:], which is an error. If you use a query type that sends requests to the server, the race window is much larger: the initial [foo:] popup doesn't disappear until it gets a request back from the server, which may be several hundred ms or more. You don't have to type *that* fast to finish a complete query and press enter in that 1s.
Possibly related to issue 8593 .
I don't know if something has changed recently to make this worse, but I feel like I am running into this daily.
Issue 8840 has been merged into this issue.
Hmm this still happens on https://gerrit-review.googlesource.com/q/-status:open you type in statu and press enter on status: and it redirects you straight to status:
Still happends (reopening) happens on gerrit-review and on http://gerrit-new.wmflabs.org/r/q/size: It should wait for you to press enter twice if it has drop down results so that you can press enter on for example status: and start typing in more and drop down shows.
What you're describing where confirming partial suggestions takes you to a query of that partial suggestion, which is a different bug. I've filed 8920.
Sign in to add a comment