Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed
Bug #891210 reported by
Chad Miller
This bug affects 17 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
Fix Committed
|
Medium
|
John Lea | ||
| Unity |
Incomplete
|
Medium
|
Unassigned | ||
| unity (Ubuntu) |
Incomplete
|
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.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in unity (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Bilal Akhtar (bilalakhtar) wrote | #2 |
| Changed in unity: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in unity (Ubuntu): | |
| importance: | Undecided → Low |
Revision history for this message
| Chad Miller (cmiller) wrote | #3 |
| 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 |
Revision history for this message
| Marco Trevisan (Treviño) (3v1n0) wrote | #4 |
Revision history for this message
| Chad Miller (cmiller) wrote Re: [Bug 891210] Re: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed | #5 |
Revision history for this message
| Palmieri (palmieri-vincent) wrote | #6 |
| tags: | added: rls-w-incoming |
| tags: |
added: rls-x-incoming removed: rls-w-incoming |
Revision history for this message
| Will Cooke (willcooke) wrote | #7 |
| Changed in unity: | |
| status: | Triaged → Incomplete |
| Changed in unity (Ubuntu): | |
| status: | Triaged → Incomplete |
| tags: | removed: rls-x-incoming |
Revision history for this message
| Henry J. Douglas (doug-the-alquimista) wrote | #8 |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.