@Manuel , from sprint 8 planning

• does this include mobile termbox as well?
• if having mul always on top is a simpler/easier implementation, do you agree with going with this implementation (over the request here of if it exists, then its on top)?

does this include mobile termbox as well?

Yes, "mobile termbox" was referred to as "new termbox" in the AC.

if having mul always on top is a simpler/easier implementation, do you agree with going with this implementation (over the request here of if it exists, then its on top)?

The "if it exists, then its on top" is unfortunately an essential intermediary part of the planned incremental release strategy (see T312097) for this:

v1.0: In the first release version, editors are not supposed to be able to create a new mul Label for an Item by default (but only if they have put mul to their babels). The reason for this is that the UX will be bad while there are no well established guidelines or helpful UI tweaks to support it.

v2.0: After the Community has created guidelines and we have linked to them in the UI we will open mul for all users by default. This is when we can change the behavior to "mul always on top".

Should this strategy add too much complexity from an engineering perspective, please let me know.

The description seems to assume that users are able to specify the order of languages in the Termbox via Babel.
I played around with this a bit, and that seems false.

With this Babel:

I'm still getting this ordering:

Note that German is in the last position, not somewhere at the top.

I just checked again and it works for me. Could you please verify that you logged in with the same account?

In T316767#8926709, @Manuel wrote:

I just checked again and it works for me. Could you please verify that you logged in with the same account?

Those screenshots are from the same account. Could you elaborate what exactly you tried and what "works for you" means in detail?

Sprint Planning Notes:

• @Manuel can investigate further regarding the babel ordering, to add a new feature to take this into account
• The easiest requirement to initially address is that the mul languages will always be set to the bottom
• Perhaps a technical investigation is also required to understand how this works

@Michael: You are right! It was just a coincidence that my tests worked. The Babel-defined rows are in alphabetical order (by language code, as Marius mentioned). I have clarified the task accordingly.

Thank you for bringing this up!

Task Breakdown Notes

• the current status quo of who sees the MUL language code on test wikidata should remain
• subtask 1 - show MUL as last language if any MUL terms exist (@Michael )
• subtask 2 - create the feature flag to always show the MUL language code (@Lucas_Werkmeister_WMDE )

Open questions:

• On which tests systems should the feature flag be enabled/disabled? E.g. enabled on Beta, disabled on Test Wikidata or vice versa @Manuel

E.g. enabled on Beta, disabled on Test Wikidata or vice versa @Manuel

Yes, that is a great idea! My suggestion would be to simulate the soft rollout phase on the system that is more similar to Wikidata (as this is what we will initially release) and always show the MUL language code on the other system (as we will still be able to test this at a later point in time).

I think this is ready for verification – we have the soft rollout state (mul shown as last language only if a term exists or babel contains mul) on Test Wikidata, and the eventual final state (mul always shown as last language) on Beta Wikidata.