You are currently working on UAT 

Bug: Fragment Matches "steal" focus from document

When I have a document open for translation in the editor, and I move the cursor to an unconfirmed segment (make the segment active), either with the mouse or by confirming the previous segment, and if Studio then finds and shows a Fragment Match, the cursor sometimes disappears from the target segment (the segment becomes inactive). I will then have to click in the target segment with the mouse in order to be able to write the translation. It seems to only happen the first time a Fragment Match is found after opening a document for translation.

Parents
  • Hello ,

    As you say

    the cursor sometimes disappears from the target segment

    It would be good to try and understand when these 'sometimes' are occuring and try and find a common denominator.

    Is this happening in single file translations? projects? specific language combinations maybe?

    Oana Nagy | QA Engineer | RWS Group

  • Hi Steven,

    As far as I have been able to determine, it happens on the first occurrence of a Fragment Match being found after opening a file for translation. Subsequent Fragment Matches do not cause the segment to lose focus. If the document is closed and later reopened, again the first occurrence of a Fragment Match will cause the segment to lose focus.

    I use Studio 2019 15.1.2.48878. I only use projects, never single-file translations. My language combinations are English and Swedish into Danish, and I have seen it happen with both. The reason I wrote "sometimes" is that I didn't want to say with 100% certainty that this only happens on the first occurrence - I cannot really do that as I can only observe this behaviour based on my actions, but I have not done a thorough test with all possible scenarios. But based on my observations, this is what happens.

    I hope this helps. If you need more specific information, please let me know and I will try to get it to you.

Reply
  • Hi Steven,

    As far as I have been able to determine, it happens on the first occurrence of a Fragment Match being found after opening a file for translation. Subsequent Fragment Matches do not cause the segment to lose focus. If the document is closed and later reopened, again the first occurrence of a Fragment Match will cause the segment to lose focus.

    I use Studio 2019 15.1.2.48878. I only use projects, never single-file translations. My language combinations are English and Swedish into Danish, and I have seen it happen with both. The reason I wrote "sometimes" is that I didn't want to say with 100% certainty that this only happens on the first occurrence - I cannot really do that as I can only observe this behaviour based on my actions, but I have not done a thorough test with all possible scenarios. But based on my observations, this is what happens.

    I hope this helps. If you need more specific information, please let me know and I will try to get it to you.

Children
No Data