Page MenuHomePhabricator

[GOAL] Iterate the mobile termbox workflow to make language fallback work
Open, Needs TriagePublicGoal

Description

Problem:
The current design of the new termbox seems fundamentally incompatible with language fallback:

We currently show a language name above the “title” label and description – what happens to this when the label and description fell back to a different language? (Possibly to different languages between the label and the description, too.)

image.png (167×206 px, 10 KB)

Unlike in the desktop termbox, the mobile termbox doesn’t have a row in the table for the current UI language – instead, the UI language is edited in the “title” section. What happens to those text inputs if the label and description fell back to other languages?

image.png (376×1 px, 34 KB)

Solution:
Modify the workflow of the new termbox so that it works identical to the workflow of the desktop termbox.

Open questions:

  • Should we better do all the changes on mobile in a second step or in parallel with desktop? (Itamar?)
  • What was the original reason to deviate from the established desktop workflow (heading not directly editable) on mobile? (search documentation @Sarai-WMDE and/or ask @Lea?)
  • We would need to locally update termbox edits to change the heading. This increases the complexity quite a bit, if I am right. Would it be an option to just not show the Label in the heading while editing on mobile? (@Sarai-WMDE?)

Original:
T312231#8362204

Event Timeline

Manuel renamed this task from [Goal] Make language fallback work on the mobile termbox to [Goal] Iterate the mobile termbox workflow to make language fallback work.Feb 15 2023, 10:35 AM
Manuel updated the task description. (Show Details)
Manuel added a subscriber: Sarai-WMDE.
Manuel renamed this task from [Goal] Iterate the mobile termbox workflow to make language fallback work to [GOAL] Iterate the mobile termbox workflow to make language fallback work.Feb 22 2023, 11:53 AM