Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed

[Chad Miller]

Once we become expert at using our machines, the delay between tapping the Super key and starting to type results is short, and the computer lags behind. I can hit Super, and start typing the name of a program, and the first few keys are lost because the search field in the Dash didn't appear until after I started typing. That ruins the search, and I must start over.

I haven't seen the source code, but surely the the UI isn't cheap to load, and even beginning to do that should be a step after starting to catch key events in a buffer to be replayed after the UI is up.

The UI having been displayed must not be a prerequisite for catching the letters of the thing I'm searching for.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bilal Akhtar (bilalakhtar)]

Would be a good idea in theory, but it may be tough to implement.

[Chad Miller (cmiller)]

Modal window 1x1 px. Grab keyboard focus. Dynamically load libraries. Load resources. Display UI.