@Pginer-WMF this happens when "display" language is the same as the source language. I have submitted a patch that fixes this case, but even more I have submitted another patch (linked to this task), that entirely removes the "display" language, since as you observed, it's not used anywhere, and we can just rely on the source language and title.

@Pginer-WMF is there any chance that there were no translated contents for other (non-lead) sections?

Moving this back to "Done" column, since the issue mentioned above is not related to this task.

After testing I can confirm that no categories are added when translating articles with infobox. Example translated article: https://no.wikipedia.org/w/index.php?title=Larry_Connor&oldid=24487357. I think we can close this task as done.

As indicated by the screencast above, the following URL parameters are being set when an article is selected inside the search screen:

• page (title of the page in display language)
• from (source language of the translation)
• to (target language of the translation)
• display (language in which the search result is being displayed. Also the language in which the page title is provided in the URL)
• step (the current step - can be either "confirm" or "translation")

As demonstrated by the screencast below, this issue no longer occurs. This task can be closed as "Done".

The screencast below follows the scenario for QA testing provided in the task description and everything seems to work as intended. @Pginer-WMF Given that all subtasks mentioned in this task are resolved - even T192065 seems to be resolved -, I believe we can close this task as "Done".

Based on the following screencast, this issue seems to be resolved. @Pginer-WMF do you think we can close this task as done?

As demonstrated by the screencast below, the dialog is properly displayed when a translation started on CX is clicked inside the draft list, and the splitting is performed when the user confirms the start of the translation. @Pginer-WMF
I think this task can be now closed as done.

@Pginer-WMF my understanding is that once we deploy these changes, the mffrequentlanguages entrypoint (i.e. the missing languages banner entrypoint) will be removed from the CX/SX instrumentation. Since, we now navigate the user to an intermediate step (the overlay where the new entrypoint cards are displayed), it will be hard to implement such instrumentation. Is my understanding correct?

@EChukwukere-WMF as I also explain in my comment above, you can test this task by blocking the translation request URL.

@KCVelaga_WMF thank you for your answers. About the "users searches for a topic", if we change the action to search we will also need a schemaId to be used with the mw.eventLog.submitInteraction method. Do you have any idea what value should be used as schemaId?

Thanks for your input @phuedx! To clarify, for the auto_translation_card action_source it makes sense to use a source_page object for the source language and the source page id. About the target page, I don't believe that the target page id offers a lot of value to be logged, as any translation can be uniquely identified by the source language, the target language and the source page id (or source page title). The same is true for translations in Content and Section Translation applications that are developed/maintained by the Language Team. It's also worth noting that for some events inside Content/Section Translation app (e.g. dashboard_open event) only the source-target language pair is needed, and no page id is used.

@KCVelaga_WMF I can verify that the return_from_section_selection event source is also properly logged (see screencast below). I'll update the schema version, to fix the issue.

@KartikMistry can you confirm if these errors still occur?

Note: for related articles, when no thumbnail exists, a placeholder image is used, as demonstrated in the screenshot below (from greek wikipedia):

Hey @KCVelaga! I have some questions regarding the instrumentation of MinT for Wikipedia Readers MVP:

1. could you please provide me the stream name for these events?
2. given that the action_context should be a string, I suppose that the auto_translation_card case should be a string in this format: sourceLanguage;targetLanguage, where sourceLanguage and targetLanguage are the values of the source and target language codes, separated by a semi-colon. Is my assumption correct?
3. The "users searches for a topic" event should be a "click" action according to the spec. My assumption would be that this event will be triggered when the user actually types a query inside the search input. Am I missing something here?

The response from the two endpoints Isaac listed above, are identical. If this is the case, it seems like a straightforward switch.