Red Hat Bugzilla – Bug 747898
'Enter' and 'Ctrl+Enter' keyboard shortcuts do not shift focus if 'Next Entry' is chosen in the navigation settings
Last modified: 2013-03-03 21:22:07 EST
Description of problem:
In the newly added settings for navigation, selecting the last item in the drop down 'next entry' partially disables the 'Enter' (if selected) and 'Ctrl+Enter' keyboard shortcuts. These shortcuts allow the users to save the current entry and to move to the next entry. However, in this case the current entry gets saved, but the focus remains on the cell when 'Enter' (if selected) or 'Ctrl+Enter' is used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to Zanata and navigate to a project of your choice. Open a file in the web editor
2. Using the settings icon on the navigation panel, select 'Enter' key saves immediately' and 'Navigation key/button options:'=>'Next Entry'
3. Start editing an entry and click 'Enter' or 'Ctrl+Enter' to save that entry.
The entry is saved, but the focus remains on the entry
The entry is saved and the focus moves to the next entry
Ideally the 'Next Entry' option should not be present in the dropdown. It already has an exclusive button on the navigation panel.
This behaviour is observed with Zanata version 1.4.2-SNAPSHOT (20111021-1207)
The reason "Next Entry" is in the dropdown is so that Enter/Ctrl-Enter can support the new modal navigation feature and still have the ability to go simply to the next row. But obviously you've found a bug with that.
But even if that feature were working, it doesn't seem to be well liked, so we can just take it out of the dropdown, and Enter/Ctrl-Enter will just go to the next row, as before.
Remove 'Next Entry' option from shortcut config.
CTRL+Enter / Enter in editor move to next entry.
With Zanata version 1.4.2-SNAPSHOT (20111024-1450)
The 'Next Entry' is removed.
Ctrl-Enter/ (Enter) moved to next entry.
However, now Ctrl-Enter /Enter does not change the NeedReview entries to Approved.
Thus, this bug is re-ASSIGNED.
Bug reported on Comment 4 fixed. See https://github.com/zanata/zanata/commit/dbe977e2c9d3f6d409dd3fab312d9f989f954445
VERIFIED with Zanata version 1.4.2-SNAPSHOT (20111025-0954)