User-Agent: Mozilla/5.0 (X11; Linux i686 (x86_64)) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30 The user's own save notifications can cause the editor to close (cancel edit). This problem can happen when clicking up and down in the table, depending on processing speed, but the most consistent trigger is based on key shortcuts. Reproducible: Always Steps to Reproduce: 1. Enter some text in a target cell (ie change the content) to force a Save upon exit. 2. Press Alt+J+K (ie Alt+J and Alt+K virtually simultaneusly). Actual Results: Cell content saved, but the save notification for that cell causes the editor to close. If the notification is for the text content as is currently in the editor, there is no need to cancel editing. Expected Results: Cell content saved; editor is open on the original target cell.
Note that this problem is currently exacerbated by bug 728858's extra save notifications.
This bug is probably related to bug 728851
If we fix bug 728858, I suppose this one won't need a high priority.
Assigning to Scrum product owner for prioritisation.
This is a serious loss of functionality of the editor. Moving this back to high.
Problem fixed along with fixes in https://bugzilla.redhat.com/show_bug.cgi?id=746870. See https://github.com/zanata/zanata/commit/0085dc7482aed3e1a9d7a8b6b6464059a81a86f3
VERIFIED with Zanata version 1.4.2-SNAPSHOT (20111020-1402)