Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ayatana Design |
Medium
|
John Lea | ||
| | Unity |
Incomplete
|
Medium
|
Unassigned | |
| | unity (Ubuntu) |
Medium
|
Unassigned | ||
Bug Description
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.
| Bilal Akhtar (bilalakhtar) wrote : | #2 |
Would be a good idea in theory, but it may be tough to implement.
| Changed in unity: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in unity (Ubuntu): | |
| importance: | Undecided → Low |
| Chad Miller (cmiller) wrote : | #3 |
Modal window 1x1 px. Grab keyboard focus. Dynamically load libraries. Load resources. Display UI.
| tags: | added: udp |
| Changed in ayatana-design: | |
| assignee: | nobody → John Lea (johnlea) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in unity: | |
| milestone: | none → backlog |
| Changed in ayatana-design: | |
| status: | Triaged → Fix Committed |
| Changed in unity: | |
| status: | Confirmed → Triaged |
| Changed in unity (Ubuntu): | |
| status: | Confirmed → Triaged |
| tags: | added: a11y |
| Changed in unity: | |
| milestone: | backlog → none |
| summary: |
- dash search should catch keyboard events immediately, not after UI is - loaded and displayed + Dash - dash search should catch keyboard events immediately, not after + UI is loaded and displayed |
| Changed in unity: | |
| importance: | Low → Medium |
| Changed in unity (Ubuntu): | |
| importance: | Low → Medium |
| Marco Trevisan (Treviño) (3v1n0) wrote : | #4 |
Mh, I can't reproduce this anymore, but I guess it might still happen on low powered machine... Any feedback?
| Chad Miller (cmiller) wrote : Re: [Bug 891210] Re: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed | #5 |
I can't reproduce now.
| Palmieri (palmieri-vincent) wrote : | #6 |
This doesn't affect me anymore, and my machine can be considered as low powered. Thanks for the fix !
| tags: | added: rls-w-incoming |
| tags: |
added: rls-x-incoming removed: rls-w-incoming |
| Will Cooke (willcooke) wrote : | #7 |
Sounds like this is not an issue any more. Untagging from rls-x-incoming and subscribing myself. Please comment if this is still an issue for you.
| Changed in unity: | |
| status: | Triaged → Incomplete |
| Changed in unity (Ubuntu): | |
| status: | Triaged → Incomplete |
| tags: | removed: rls-x-incoming |
It still affects me. Low powered machine. After pressing the Super key, i type something while the UI is not loaded yet and it doesn't catch anything I typed before. Opening dash through other methods work. Only Super causes a massive 2 second delay. Intel Graphics. Ubuntu 16.04.1
Status changed to 'Confirmed' because the bug affects multiple users.