I would say the behavior isn't better with the two patches merged. The problem from the description still exists and the MT percentage in the issue card no longer updates while the user types.
Sun, Sep 23
Fri, Sep 21
Thu, Sep 20
Wed, Sep 19
Tue, Sep 18
Mon, Sep 17
Sun, Sep 16
Fri, Sep 14
Thu, Sep 13
The merged patch completes the third requirement - "Delay the check of the current paragraph after the user starts editing it".
Wed, Sep 12
Tue, Sep 11
This is not configurable in Mediawiki notifications. Options are short (5 sec) and long (30 sec).
So, duration will need to be five second, instead of three.
I have updated the description after reviewing the patch from @santhosh that takes the latest timestamp into account when restoring content. The patch is good, but it's futile unless the behavior from newly updated description is not changed.
This still happens, here is another example. With English to Spanish as language pair, I got suggestion to translate en:Spanish_Colonial_architecture. When I choose to translate that page and the dialog opens, Content Translation correctly informs that page already exists in Spanish:
@leila is correct about why this happens. Wikidata item only has English version listed in this case. Article on enwiki has the following wikitext, which links to eswiki article section:
[[es:Arquitectura de España#Arquitectura colonial]]
Mon, Sep 10
@Pginer-WMF I have some design questions.
The merged patch only adds warning for block level templates. Implementation of other specs is in progress.
Sun, Sep 9
Sat, Sep 8
Fri, Sep 7
I have tried again to translate "Football League First Division (1892–1992)" section of en:List_of_English_football_champions to Spanish using Apertium.
After the patch, the section no longer fails with the reported error. Network call to add paragraph with big table took 28 seconds to complete, while table showed 10 seconds later. Saving took 8 seconds.
Thu, Sep 6
Wed, Sep 5
Yes, when default MT provider fails, we fallback to adapting source and the passed node is of type ve.dm.CXPlaceholderNode, which is detached from the document.
I have made slight corrections to the structure of your report and fixed some typos.
Moving back to QA, since cxserver is updated now
Tue, Sep 4
Mon, Sep 3
Yes, that was an intention. To quote @Neil_P._Quinn_WMF:
For ease of analysis, I think we should set both tags on CX2 revisions: contenttranslation marking it as a CX edit generally, and contenttranslation-v2 making it as a version 2 edit specifically. That way, the contenttranslation tag will cover the first history, and we can then stop setting and querying the v2 tag once v1 has been fully replaced.