Hey @Manuel. I have a couple of clarifying questions:

1. What is it meant by "WHEN an empty Label/Alias is edited on desktop (or mobile), THEN the placeholder value disappears"? Does this refer to the fact that the MUL placeholder is replaced if a label is manually entered for a specific language? I think this should be made clearer in the tasks' descriptions.

2. I believe that, in this task and the mobile one (which appears to group viewing and editing?), it should be documented at which point the new MUL label or alias is added to all languages. The BDDs seem to only capture the scenario in which the label already exists, leaving out the addition of a new MUL label. If my notes are correct, I think that what was agreed in our last conversation was:

GIVEN an Item without a MUL Label/Alias
WHEN the MUL Label/Alias is added on desktop (or mobile)
AND the user publishes their changes to the termbox
THEN the default Label/Alias placeholder value of all languages is replaced by a placeholder that matches the new MUL Label/Alias

We might need to investigate how technically feasible and costly this might be as part of this group of tasks.

Hey @Sarai-WMDE, thank you for looking into this! I tried to clarify things based on your comment. What do you think?

Sprint Planning Notes

• If there is no mul language, the old placeholder should be kept
• There is no intention to make the editing experience reactive, if during the same edit the mul label is removed, then the placeholder will only update post publishing changes

Some context for this task:

Lydia, Sarai, and I are still discussing if we want to...

A. Show placeholders for Aliases if in edit mode. In this case there would be an additional AC: Placeholders for Aliases can only take 2 lines + ellipsis (mockup will be updated soon)

B. Never show placeholders for Aliases (also not in edit mode). As this would be a UI change independent of mul, we would present a separate task for this.

You can expect an update on this from us later today.

We are going with placeholders for Labels AND Aliases in the editing mode. I have clarified the task accordingly.

Also, we have added limiting the placeholders for Labels and Aliases in both viewing and editing modes to take max 2 lines as a separate task (T340133).

As discussed, I closed the separate task T340133: MUL - Truncate placeholders for Aliases and instead added the specifications to this task.

@Sarai-WMDE: Would it be appropriate to move the mockup from the other task? Also, if we do not truncate Labels, maybe we should also not truncate Alises for now. This would mean striking the "Aliases (tbc)" AC (plus the respective description in the notes section).

Task breakdown notes:

• This will probably touch some of the same files as related changes (see T338302, T339103), i.e. somewhere in view/resources/jquery/wikibase/.
• We expect that the Labels and Aliases parts can be done separately (see subtasks), but it might make more sense to finish the Labels part before starting the Aliases part, so that we can use what we learned about how best to implement this. We might not work on the tasks in parallel. Aliases no longer in scope.
• For the ellipsis, we can use the ellipsis message in MediaWiki core. (We’ll probably need to add it to our ResourceLoader module to have it available in JS, but we don’t need a new message for it.) Aliases no longer in scope.

Questions:

Release to test.wikidata.org

@Manuel does this mean you want a separate feature flag for this? Or can it just roll out with the train? (The whole mul feature will still be disabled on Wikidata.)

Hi @Lucas_Werkmeister_WMDE, I just wanted to make sure that this is released only on a test system and not yet on Wikidata. So we will need no separate feature flag for this. Thank you for asking!

See T307274: Display fallback labels and descriptions as placeholder in termbox, which proposes:

1. The label placeholder should be the nearest label fallback of the term (e.g. if an item have both German and mul label and one who want to add a Bavarian label, the German label will be displayed as fallback)
2. Same fallback also applies to descriptions

Hi @Bugreporter, thank you for the suggestion! We'll investigate!

Post re-scope task breakdown:

• Whoever picks this task up coordinates with the engineer assigned to T340832 to identify dependencies between the stories.

Change 942627 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/Wikibase@master] Show fallback labels as placeholders while editing

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

Change 942627 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Show fallback labels as placeholders while editing

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

You should now be able to verify the fallback when editing an Item on beta, for example: https://wikidata.beta.wmflabs.org/wiki/Q522693

This should now be ready to be verified by product on test.wikidata.org