Last modified: 2013-06-09 18:32:38 UTC
When I press "save and open next", the page "jump", and the newly opened translation textbox ends up slightly over the top of the screen. It does not happen always, but often enough. Seen at translatewiki.net on Win7 / Chrome 23.0.1271.64 m. My guess is that this is a timing issue: two AJAX requests are launched, one to save the old translation and hide its box, the other to load the new translation and open its box. The second positions the new box to the top of the screen; if the first finishes later, it scrolls the page up (as a portion of it was hidden) and the new box moves out of the screen. Together with bug 41464, these two problems are very disruptive when translating lots of short texts.
I don't understand, is this a bit like bug 34443 (see video there)?
Something like that, but more disruptive. What did you use for the video? I can try to record the bug.
(In reply to comment #2) > Something like that, but more disruptive. I've not experienced it yet but I've not tried right now. > What did you use for the video? I can > try to record the bug. I don't remember exactly; probably RecordMyDesktop, I don't know software for Windows.
I know this behavior and it is not the same as bug 34443.
This seems to be related to ULS/IME. I see a keyboard icon appearing and disappearing at the bottom of the page. I just took a look at this with Niklas after getting annoyed myself. Niklas suggests to add IME support explicitly in the translation editor to prevent this. In Monday's daily of the Language Engineering team, I'll discuss this issue with Santhosh (also added to CC now).
Can you test the new translation editor at translatewiki.net/wiki/Special:Translate?tux=1 to see if it has the same issue or not?
Does not happen with the new interface, the positioning of the new window is perfect.
Lowering prio&severity in favor of trying to get TUX out as soon as possible rather than actually fixing this bug now.
The is about the old translation editor, which will no longer receive bug fixes. The good thing is, that the current translation editor does not have this problem.
