Description of problem:
When typing in the TM search field, typing j or k causes a navigation event which clears the text in the TM search field (because a new TM search is triggered)
Version-Release number of selected component (if applicable):
1.4.3-SNAPSHOT and 1.5-SNAPSHOT
Steps to Reproduce:
1.Sign in to translation editor
2.Click to focus on the TM search box
3.Type "girls just wanna have fun"
navigation event clears "girls j"
search box has "ust wanna have fun"
no navigation occurs
search box has "girls just wanna have fun"
Something similar for the full text search box of the worksspace - unable to type letters J and K in the search box, J and K keystrokes are simply being ignored, subsequent letters type fine.
On the other hand, typing J and K in the TM search box works fine for me.
Looking at Zanata version 1.4.2 (20111031-0915) here.
J and K in the full text search box of the workspace is causing a navigation event in the loaded document (you just don't see it because the editor table is hidden):
1. open a document with 3 or more text units, select the first row
2. click project name to see doc list
3. click search box and type "kayak"
4. click project name to return to document
- "aya" in search box
- third TU is selected
- "kayak" in search box
- first TU still selected
Apparently IBUS input method intercept key capturing and provide a temporary workaround for this bug.
Problem occurs due to the 'J' and 'K' capturing for navigation mode in translation table. Changed shortcut key to use ALT+J and ALT+K for navigation mode to eliminate any possible text field problem with single char capturing.
Fixed in 1.5
Apply fixes in 1.4
VERIFIED with Zanata version 1.4.3-alpha-3-SNAPSHOT (20111128-1320)
and Zanata version 1.5-SNAPSHOT (20111129-0927)