Bug 729843 - Please change shortcut key of 'ESC' for 'Cancel' to something else, or remove 'Cancel' button.
Summary: Please change shortcut key of 'ESC' for 'Cancel' to something else, or remove...
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI, Usability
Version: 1.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: David Mason
QA Contact: Ding-Yi Chen
Depends On:
Blocks: Zanata-1.4
TreeView+ depends on / blocked
Reported: 2011-08-11 02:31 UTC by Sean Flanigan
Modified: 2012-11-27 07:20 UTC (History)
1 user (show)

Fixed In Version: 1.4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 880500 (view as bug list)
Last Closed: 2011-10-28 07:05:35 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 747157 0 unspecified CLOSED Editor Configuration: Esc key to close editor option 2021-02-22 00:41:40 UTC

Internal Links: 747157

Description Sean Flanigan 2011-08-11 02:31:50 UTC
Description of problem:

For Japanese, input process for a word is: 
 type in by sounds
 -> determine the ending of the word
 -> convert to Japanese (first candidate)
 -> show other candidates list (if first one is not right and mostly not right)
 -> choose right candidate from the list
 -> determine translation. 

Any stage, translator can go back if she wants. For
example, translator can return from 'show other candidates list' back to
'convert first candidate' by pressing 'ESC' key. However in zanata, if
translator accidentally press 'ESC' twice, entire input just simply is
cancelled. This hurts especially when translator lost lengthy translation.

Version-Release number of selected component (if applicable):

Additional info:

From noriko@redhat.com

Comment 1 David Mason 2011-08-11 03:04:19 UTC
Pushed to master and 1.4 branches

Comment 2 David Mason 2011-08-11 06:14:46 UTC
Also removed 'Esc' hint from tool tip of cancel button.

Comment 3 Ding-Yi Chen 2011-09-06 04:08:04 UTC
VERIFIED with Zanata version 1.4-SNAPSHOT (20110901-1705)

Note You need to log in before you can comment on or make changes to this bug.