These issues seem to have been fixed already. More specifically, about Content Translation (desktop), the page is pre-selected properly as demonstrated in the following screencast:

Regarding the entrypoint for Section Translation (mobile), the issue seems to be the same as the one capture in T328939, which has been already fixed and merged, and will be deployed soon. @Pginer-WMF do you think we could consider this task as done or move this to "Check after deployment" column, so that is reviewed by QA when the fix is deployed?

In T311820#8704624, @ngkountas wrote:

These issues seem to have been fixed already. More specifically, about Content Translation (desktop), the page is pre-selected properly as demonstrated in the following screencast:

The main scenario defined in the ticket does not. seem to be currently supported yet:

This ticket proposes to ensure that the page is pre-selected in these cases too. The user is expected to reach the confirmation step with the page and source languages pre-filled and the target language unselected. The options to continue will be disabled until the target language is selected.

In order to test this you need to tap in the "more" ("...") option instead of a specific language ("Ελληνικά" in the screencast example)

@Pginer-WMF You are right. I misread the description. Sadly, this is not a bug, it's a missing feature. Since the publishing happens in the target wiki of the translation, we need to redirect the user to the Content/Section Translation application inside the target wiki. However, since there is no target language, it is unclear where the user should be redirected. In this sense, selecting a wiki to redirect to, is basically equivalent to select a target language. Do you have any suggestions how we should handle this case? FYI this doesn't seem like a quick fix to me, this is why I'm having some second thoughts if we should invest effort in this, or we should just fallback to a simple solution like selecting the first suggested language as target language.

In T311820#8722148, @ngkountas wrote:

Do you have any suggestions how we should handle this case? FYI this doesn't seem like a quick fix to me, this is why I'm having some second thoughts if we should invest effort in this, or we should just fallback to a simple solution like selecting the first suggested language as target language.

I think it makes sense to try a simple solution to try. Later, based on observation, we can decide whether a more elaborated option may be needed.

Selecting the first suggested language as target language seems a valid approach. Users selecting the "..." will have a simple path to select their desired language and start the translation. Much better than losing the article selection.

More generally, one consideration: the redirect is important before the translation starts but it does not need to happen necessarily at the entry point stage. Would it be possible for this scenario to direct the user to Content Translation on the source wiki instead of the target one with the language selection set to Source -> empty. In this way, once the user selects the target language, the user will be redirected to the appropriate wiki. This would require two aspects:

• Making the button to continue inactive when the language selector does not have a specific pair selected, and active once the user selects a target language.
• Having Section Translation available in all languages. Currently it is not the case, and people on English Wikipedia will get to an error page in this scenario (making things worse than current). So this would be a blocker for the approach.

Change 942057 had a related patch set uploaded (by Wangombe; author: Wangombe):

[mediawiki/extensions/ContentTranslation@master] CX: Pre-select target language in Uls Entrypoint

https://gerrit.wikimedia.org/r/942057

Change 942057 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] CX: Pre-select target language in Uls Entrypoint

https://gerrit.wikimedia.org/r/942057

The implemented fix is to select the first language as the target language and redirect the user to CX. when the ellipses are clicked on. 'Missing in x and y language' would otherwise not appear as an option in the ULS thus there will always be a target language to set.