Red Hat Bugzilla – Bug 836142
Shortcuts for highlighting text is instead inserting TM result (Alt+Shift+keypad conflict) [1.7]
Last modified: 2012-09-12 20:33:33 EDT
+++ This bug was initially created as a clone of Bug #834979 +++
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Using standard keyboard combinations for highlighting text is instead inserting a TM result.
Steps to Reproduce:
1. Open existing translation in editor, putting the cursor at the end of the string.
2. Hold down Ctrl+Shift, then additionally press left arrow key.
The 4th TM match is being inserted into the editor.
Holding down Ctrl+Shift, with each time I hit the left arrow key, he text should be highlighted word by word -- this is standard text editor behaviour.
Severity medium/high because this behaviour is really unexpected, deletes existing translation inserting and approving a different translation, and there is no undo functionality any more to fix what happened.
--- Additional comment from firstname.lastname@example.org on 2012-06-26 09:54:20 EST ---
Suggest copy from TM shortcut to be change from ALT+SHIFT + 1,2,3,4 to
CTRL+ATL + 1,2,3,4 to prevent conflict of keypad 4 with left arrow button as result of Shift key being press.
--- Additional comment from email@example.com on 2012-06-26 13:18:40 EST ---
Fixed in 1.6.1
--- Additional comment from firstname.lastname@example.org on 2012-06-28 18:17:24 EST ---
VERIFIED with Zanata version 1.6.1-SNAPSHOT (20120628-0014)
But problem remains with Zanata version 1.7-SNAPSHOT (20120626-0025)
Turns out my original bug report (https://bugzilla.redhat.com/show_bug.cgi?id=834979) should have been against the 1.7 version, THAT'S where I've noticed the problem. Sorry for any confusion.
Any hope to have this fixed and deployed for 1.7.x soon?
I've stalled my current translation assignments because it's too painful working with this bug.
Um, 1.7.0 hasn't been released yet.
Oh gosh... of course, sorry. I'm getting ahead of myself here.
Nevermind, and thank god it's friday. :-D
Issue fixed in 1.7 along with fixes from
VERIFIED with 1.7-SNAPSHOT (20120705-0026)