Page MenuHomePhabricator

Basic support for translating in multiple sessions on mobile
Closed, ResolvedPublic

Description

When translating articles and sections, mobile users are required to work in a single session. In contrast, desktop users can work on a translation on multiple sessions thanks to the work being auto-saved before publishing.

This ticket proposes to create the basic support for working on a translaiton in multiple sessions. This epic ticket covers auto-saving, warning and continuing an existing translation (sub-tickets linked below):

Auto-saving process (T322517)

  • Saving can be triggered after users apply a translation for a sentence (using the apply button or saving an edit).
  • No feedback or indication is provided to communicate saving is in-progress for now.
  • Publishing a translation makes it change their status from in-progress to published.

Leaving a translation (T322518)

Currently, trying to leave a translation shows always a warning (T270484). This will change:

  • Trying to leave a translation where there are changes pending to be saved should show an alert warning the user that changes may get lost.
  • Trying to leave when changes are saved, or when there is no change made yet, should just return to the dashboard without warning.

Continuing translations (T322521)

  • Starting a translation for an article/section for which an in-progress, will result in continuing the translation.
  • Starting a translation for an article/section for which an in-progress article does not exist, was removed by the user, or it has been published, will result on a new translation (not continuing a previous draft). This is important to prevent issues such as the ones captured in T192065.

Follow-ups

Note that listing the in-progress translations is not part of the scope of this ticket. Thus, continuing an existing translaiton will be performed by searching for the same content to translate, and there won't be yet a control to discard an in-progress translation. Follow-up tickets will provide options to view in-progress translations (T260165), published ones (T260166) and switch between these views (T319181).

Scenario for QA testing

With the above, the following scenario should work as described:

  1. Start a translation from English to Igbo for "Paneer".
  2. Edit the translation for a sentence and apply the proposed translation for the next one.
  3. Leave the translation editor and return to the dashboard.
  4. Depending on how the previous step was performed, a warning may appear to indicate that saving has not complete. Wait and try again if that is the case.
  5. Start again a translation from English to Igbo for "Paneer"
  6. The translation editor loads with the previously translated sentences present.
  7. Publish the translation in the sandbox.
  8. Start again a translation from English to Igbo for "Paneer"
  9. The translation editor loads without any previous translations.

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedPginer-WMF
Resolvedngkountas
Resolvedngkountas
Resolvedngkountas
ResolvedBUG REPORTngkountas
Resolvedngkountas
Resolvedngkountas
Resolvedngkountas
Resolvedngkountas
Resolvedngkountas
ResolvedWangombe
ResolvedWangombe
ResolvedBUG REPORTngkountas
ResolvedBUG REPORTngkountas
OpenBUG REPORTNone

Event Timeline

Pginer-WMF renamed this task from Basic support for auto-saving on mobile to Basic support for auto-saving translations on mobile.
Pginer-WMF triaged this task as Medium priority.
Pginer-WMF raised the priority of this task from Medium to High.
Pginer-WMF renamed this task from Basic support for auto-saving translations on mobile to Basic support for translating in multiple sessions on mobile.Nov 7 2022, 10:39 AM
Pginer-WMF added a project: Epic.
Pginer-WMF updated the task description. (Show Details)
Pginer-WMF updated the task description. (Show Details)
Nikerabbit changed the task status from Open to In Progress.Jan 8 2024, 7:53 AM

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".

Yes all the tasks under this has been closed so we can close this epic

Pginer-WMF claimed this task.

Main support is complete. Good work!
New issues detected can have their own tickets such as T368517.