Change 730039 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/ContentTranslation@master] SXTranslationConfirmer: Go to previous route on back button click

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

Change 730039 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] SXTranslationConfirmer: Go to previous route on back button click

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

Change 731310 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.1.0+20211018

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

Change 731310 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.1.0+20211018

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

if we click the "select section to translate" button after the first screen of the search, then the X back button doesn't work as expected on this task, it goes back to the dashboard instead of the search screen

In T290455#7483507, @Jpita wrote:

if we click the "select section to translate" button after the first screen of the search, then the X back button doesn't work as expected on this task, it goes back to the dashboard instead of the search screen

Thanks for capturing that part of the workflow. I think we can consider adjusting that as part of another ticket if needed.

I think once the user has committed to the translation, cancelling it make sense to go to the dashboard. However, it is not totally clear where users perceive that point (is moving beyond the confirm step? is when they reach the editor?). We may want to observe through which steps the users repeatedly iterate when searching for a section to translate ( @Easikingarmager this may be relevant for upcoming research observations).

This task was focused on keeping the search context up to the confirmation step since there was a clear iteration pattern of searching for another article. We may need to expand it further if looking into the detail of the section list is actually part of such process. For this, I think it makes sense to wait for some more user observations and use of the tool.

So I think the current ticket can be resolved if the navigation from the confirmation step to the search step is working.