Bug 876131 - Keyboard setup type-lookahead is wonky.
Summary: Keyboard setup type-lookahead is wonky.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-13 12:21 UTC by Andreas Tunek
Modified: 2013-05-10 02:00 UTC (History)
7 users (show)

Fixed In Version: anaconda-18.30-1
Clone Of:
Environment:
Last Closed: 2013-05-10 02:00:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
keyboard pressed "c" (68.20 KB, image/png)
2012-11-13 12:21 UTC, Andreas Tunek 		no flags Details
keyboard pressed "chi" (72.01 KB, image/png)
2012-11-13 12:22 UTC, Andreas Tunek 		no flags Details
View All

Description Andreas Tunek 2012-11-13 12:21:10 UTC 
Created attachment 644081 [details]
keyboard pressed "c"

Description of problem:
In the keyboard setup (see screen shots) if you type "c", it highlights chinese. If you type "chi" it highlights french. See the two attached screen shots.
Comment 1 Andreas Tunek 2012-11-13 12:22:07 UTC 
Created attachment 644083 [details]
keyboard pressed "chi"
Comment 2 Vratislav Podzimek 2012-11-14 08:20:50 UTC 
Searching in the list should be disabled. The only supported way is to type something into the filtering TextEntry below the list. Patch for this pushed to master.
Comment 3 Adam Williamson 2012-11-23 06:44:45 UTC 
vratislav, when exactly should this be fixed? Beta (18.28/18.29.x) or post-Beta (18.30+)? Can you updated fixed-in-version? Thanks!
Comment 4 Vratislav Podzimek 2012-11-27 09:17:59 UTC 
(In reply to comment #3)
> vratislav, when exactly should this be fixed? Beta (18.28/18.29.x) or
> post-Beta (18.30+)? Can you updated fixed-in-version? Thanks!
This is fixed in anaconda-18.30-1.
Comment 5 Adam Williamson 2013-05-10 02:00:23 UTC 
Tested in F19 Beta TC3, confirmed fixed.
Note You need to log in before you can comment on or make changes to this bug.