Page MenuHomePhabricator

Revisit the language selector control UX, and see if we can improve it to something similar to the ULS control
Closed, ResolvedPublic


(1) Language drop-down selection text field doesn't recognize codes for languages from ISO 639-2 Language Code List

Screen Shot 2023-05-03 at 1.19.08 PM.png (1×1 px, 167 KB)

Note: the examples where lang codes are recognized:

Screen Shot 2023-05-03 at 1.22.34 PM.png (796×1 px, 77 KB)
Screen Shot 2023-05-03 at 1.23.38 PM.png (902×1 px, 127 KB)

(2) Does Language selection should be that granular? i.e. British English, Canadian English etc
(3) "English" is displayed as a default lang. Clicking in the field will display "No results found"

Screen Shot 2023-05-03 at 1.36.59 PM.png (468×1 px, 71 KB)

Typing "English" will display more suggestions:
Screen Shot 2023-05-03 at 1.36.33 PM.png (710×1 px, 131 KB)

(4) When a language is selected from suggestions, that option will be removed from the list.
Might be confusing for users who would change their lang selection several times during their editing session.

  • a user starts typing "English" in the Language text field
  • a user selects "Canadian English"
  • then decides to go back to just "English", selects "English" option
  • at the end of the editing session, decides to return to "Canadian English". That option won't be present on the list anymore:
Screen Shot 2023-05-03 at 1.28.55 PM.png (984×1 px, 154 KB)
Screen Shot 2023-05-03 at 1.30.30 PM.png (1×1 px, 170 KB)

Event Timeline

Etonkovidova renamed this task from [QA task] Evaluation Special:CreateZObject page to [QA task] Special:CreateZObject page - language selection.Jul 7 2023, 8:18 PM
Etonkovidova updated the task description. (Show Details)

Per discussion with Elena yesterday, we're marking this as Resolved and following up with a broader post-launch task to re-visit the flow of the language selector.

Jdforrester-WMF reopened this task as Open.
Jdforrester-WMF removed Etonkovidova as the assignee of this task.

Actually, let's just use this task?

Jdforrester-WMF renamed this task from [QA task] Special:CreateZObject page - language selection to Revisit the language selector control UX, and see if we can improve it to something similar to the ULS control.Jul 19 2023, 12:05 AM
Jdforrester-WMF added a project: Epic.

there might be an opportunity to collaborate with the language team here! i was recently chatting with @Pginer-WMF and he told me that the language team is working on Codex-powered ULS, more on T287860: Support for a Responsive Language Selector. We could share with them our different use cases, and explore together how the next gen ULS might be able to support wikifunctions too, both for the global language selector, but also for language selection across the different views.

Hello! Does this task still exist as an issue or are there any updates to this?

Hello! Does this task still exist as an issue or are there any updates to this?

i'd say this is still an issue, but we have to balance between what we think it's critical to do in the near term, and what can wait on the new version of the ULS, that we could (maybe?) also use on wikifunctions.

the tradeoff here is that everything we do for improving the global language selection is going to be developed, and maintained by us. so, we have to carefully decide what we think is worth doing in the short-term, and what instead can wait for longer, until the ULS is able to cover also for our own use cases on WF.

@ecarg -you're right - the overall state of the language selector has been improved. I re-checked the reported cases in the task description. Below is the summary of the current state:
DONE (1) The language codes are recognized now (checked on wikifunctions beta and wikifunctions wmf.1) and the matching language will be the top suggestion. Also, there are more information added to the suggestions - the language code, a description, e.g. Natural language or some info on the lang script if the matching search result is found: e.g. Devangari script. That improves user experience in selecting the language they intend to add/select.


`it' -> Italian
Screen Shot 2024-04-18 at 12.46.32 PM.png (1×1 px, 178 KB)
tsi -> Tsischian
Screen Shot 2024-04-18 at 1.00.58 PM.png (1×1 px, 111 KB)
dev - languages with Devangari script in description
Screen Shot 2024-04-18 at 1.15.52 PM.png (1×1 px, 123 KB)

When search doesn't return matches - the languages will be displayed in the default order with the indication that the search term was not found:

Screen Shot 2024-04-18 at 1.10.37 PM.png (1×1 px, 118 KB)

The other cases
(2) - the granularity of suggested languages is still present - i.e Canadian English and Simple English will be in suggested languages list. I'm not sure whether is it an actual issue though. What, for example, should happen if a user selects Simple Englishin terms what is an expected impact on UI (or the backend). However, this is a minor issue, pinging @AAlhazwani-WMF.

Screen Shot 2024-04-18 at 1.27.46 PM.png (1×1 px, 125 KB)
Screen Shot 2024-04-18 at 1.02.13 PM.png (1×1 px, 125 KB)

DONE (3), (4) - are not present anymore.

thank you @Etonkovidova! agreed with you. i'll move this to verify in prod, even if it's already being done! :)