Page MenuHomePhabricator

Implement product-wide solution for fallback labels
Open, MediumPublic

Assigned To
None
Authored By
AAlhazwani-WMF
Jun 28 2023, 9:27 AM
Referenced Files
F41805598: image.png
Feb 7 2024, 5:20 PM
F41805558: image.png
Feb 7 2024, 5:20 PM
F37121924: image.png
Jun 28 2023, 9:27 AM
F37121911: image.png
Jun 28 2023, 9:27 AM

Description

We display fallback (localized) labels via a chip component with the language ISO code that we currently use for the monolingual text component.

image.png (2,374×1,714 px, 207 KB)

The chips are currently visible for things under the contents area and the header/title bar, but we don't show them in other instances like:

  • the function definition under the details tab on the function page
  • the function implementations and testers tables
  • the about widget
  • the function explorer widget
  • the testers/implementation widget

We designed a proposal to display fallback labels throughout the product, with an accompanying widget for highlighting the missing labels in the user language, see T329103.

As a first iteration, we can implement only the subtle dashed underline for fallback labels (and display the language name via the title attribute on hover), and later evaluate if it's worth it to add the widget too.

image.png (2,560×1,600 px, 192 KB)

Event Timeline

note to self, found this neat visual treatment on slack for uncomplete usernames

image.png (312×184 px, 16 KB)

what if we would opt for something similar, very quick very rough mockup

image.png (176×88 px, 6 KB)

during one of the last design review, we presented a preview of the upcoming changes to the about widget. based on that proposal, the general consensus for when in need to display fallback content was the following:

  • display content only once (instead of duplicating the UI), eg. with an inline fallback language, similar to some examples on wikipedia.
  • (wikipedia) editors, and multilingual people, are used to mixed-content being displayed inline. think of CJK wikipedias with latin characters, but even content from regions where people speak multiple languages with one alphabet, eg. canada, switzerland, ...