Improve UX regarding the input character length limit in command palette

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

This issue was started from another issue #520496 (closed). While the UI shown in #520496 (closed) is not the command palette and the serving backend is also different, users would run into (UX) issue that is going to be described in this issue.

When users start a search in the command palette, the UI would not redirect to the search result page if the input character length is less than 3. There's no visual indication why this happens either.

Steps to reproduce

  1. Go to an issue page
  2. Hit / key to open the command palette
  3. Enter ab or anything one or two characters string in the input box and hit return

What is the current bug behavior?

It won't redirect to the search result page or any page.

What is the expected correct behavior?

It should either give users some hint on the minimum character length limit or just redirect the user to the search result page.

Relevant logs and/or screenshots

Possible fixes

It should either give users some hint on the minimum character length limit or just redirect the user to the search result page.

I think the behavior is similar as it's mentioned in #396873 (closed) which was before the command palette was released. But if you expand the design in that issue description, it suggested adding a hint to tell users the input length limit.

Please also see Inconsistent search results with recent items a... (#442001) for related input character length discussion.

Edited by 🤖 GitLab Bot 🤖