Page MenuHomePhabricator
Create Task
Maniphest T407349

Display all wishlist parts in current UI language
Closed, ResolvedPublic5 Estimated Story Points
Actions

Assigned To
• MusikAnimal
Authored By
Samwilson
Oct 15 2025, 12:07 PM
Tags
Referenced Files
F71578111: 2026-01-20_08-47-09.webm
Tue, Jan 20, 6:12 PM
F71578109: 2026-01-20_08-45-02.webm
Tue, Jan 20, 6:12 PM
F71578108: 2026-01-20_08-41-56.webm
Tue, Jan 20, 6:12 PM
F71449336: 2026-01-05_12-35-49.mp4
Jan 5 2026, 8:38 PM
F71449102: 2026-01-05_12-01-16.png
Jan 5 2026, 8:08 PM
F71449056: 2026-01-05_11-40-31.mp4
Jan 5 2026, 8:08 PM
Subscribers
Aklapper
dmaza
GMikesell-WMF
HMonroy
• MusikAnimal
Samwilson

Description

This is a follow-up to Test Case 9 of T399514.

On the wishlist homepage, we show the focus area index in the content language, but the wish index in the UI language. Additionally, the FA titles in the filter field are shown in the content language, in a field that has a label in the UI language.

Derived Requirement

Ensure that all wishlist-related UI elements on the wishlist homepage are consistently displayed in the current UI language. This includes the focus area index, wish index, and focus area titles shown within filter controls. No wishlist content or labels should fall back to the content language when a UI language is explicitly set.

Test Steps

Test Case 1: Display Focus Area Index in UI Language

Preconditions

  • The wishlist homepage is accessible.
  • The UI language is set to a language different from the wiki content language.
  1. Open Wikipedia.
  2. Change the UI language to a non-default language.
  3. Navigate to the wishlist homepage.
  4. Observe the focus area index section.
  5. ✅❓❌⬜ AC1: Confirm that all focus area titles in the focus area index are displayed in the current UI language and not in the content language.

Test Case 2: Display Wish Index in UI Language

Preconditions

  • Same as Test Case 1.
  1. Navigate to the wishlist homepage with the UI language set.
  2. Observe the list of wishes displayed in the wish index.
  3. ✅❓❌⬜ AC2: Confirm that all wish titles and related textual elements in the wish index are displayed in the current UI language.

Test Case 3: Display Focus Area Filter Values in UI Language

Preconditions

  • Same as Test Case 1.
  • At least one focus area exists.
  1. Navigate to the wishlist homepage.
  2. Locate the focus area filter field.
  3. Open or interact with the focus area filter.
  4. Observe the focus area titles shown as selectable values.
  5. ✅❓❌⬜ AC3: Confirm that focus area titles within the filter field are displayed in the current UI language and match the language of the filter label.

QA Results - Meta Beta

ACStatusDetails
1✅T407349#11538709
2✅T407349#11538709
3✅T407349#11538709

Details

Related Changes in Gerrit:
SubjectRepoBranchLines +/-
Add user dismissable CSS class to cdx-messagemediawiki/extensions/CommunityRequestsmaster+1 -1
Render everything possible in the user interface languagemediawiki/extensions/CommunityRequestsmaster+153 -97
Use user language in parser function renderersmediawiki/extensions/CommunityRequestsmaster+19 -13
Customize query in gerrit

Related Objects
Search...

Event Timeline

Samwilson created this task.Oct 15 2025, 12:07 PM
Restricted Application added a project: Community-Tech. · View Herald TranscriptOct 15 2025, 12:07 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Samwilson mentioned this in T399514: Add volunteer-facing filters to wishlist.Oct 15 2025, 12:07 PM
gerritbot added a comment.Oct 15 2025, 12:09 PM

Change #1196210 had a related patch set uploaded (by Samwilson; author: Samwilson):

[mediawiki/extensions/CommunityRequests@master] Use user language in parser function renderers

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

gerritbot added a project: Patch-For-Review.Oct 15 2025, 12:09 PM
Samwilson added a comment.Oct 15 2025, 12:12 PM

The other option here is to do it the other way around, and show the UI elements in the content language. That would mean that all elements on a page would conform to the language of the Translate selector at the top (and for wikis without Translate, it'd be the site language). There are usually more interface languages than target languages for page translations, so that'd reduce the number of people interacting with the filters etc. in their own language.

A_smart_kitten added a project: I18n.Oct 15 2025, 12:51 PM
• MusikAnimal moved this task from Backlog to General on the MediaWiki-extensions-CommunityRequests board.Oct 23 2025, 9:55 PM
gerritbot added a comment.Oct 27 2025, 4:27 PM

Change #1196210 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Use user language in parser function renderers

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

jenkins-bot mentioned this in rECOR2a638821b506: Use user language in parser function renderers.Oct 27 2025, 4:28 PM
Maintenance_bot removed a project: Patch-For-Review.Oct 27 2025, 4:30 PM
ReleaseTaggerBot added a project: MW-1.45-notes (1.45.0-wmf.25; 2025-10-28).Oct 27 2025, 5:00 PM
mikez-WMF assigned this task to Samwilson.Oct 28 2025, 8:06 PM
• MusikAnimal edited projects, added Community-Tech (Sea Lion Squad); removed Community-Tech.Oct 28 2025, 8:06 PM
• MusikAnimal moved this task from Backlog - groomed to QA on the Community-Tech (Sea Lion Squad) board.Nov 1 2025, 7:46 AM
• MusikAnimal mentioned this in T406368: Focus Area index cards require cache purge before new entities appear when table is in Hebrew.Nov 5 2025, 9:01 AM
• MusikAnimal moved this task from QA to In Development on the Community-Tech (Sea Lion Squad) board.Nov 11 2025, 10:05 PM
• MusikAnimal subscribed.

So I think the big part missing here is to get the parser output as a whole to be in the user interface language, and then set lang and dir attributes for user-submitted content (like the description). That will make the MinT integration much more efficient, which is needed for T408160: Make the MinT translation preference on by default if possible.

It seems like setting the ParserOutput language in the ParserAfterTidy hooks fixes most everything. I've got a WIP patch for that I will submit here, and move this back into development since I don't think we're quite ready for QA given how much userlang/pagelang mismatches there are currently. I'm assuming @Samwilson wasn't actively working on this task. If so, sorry if I'm stepping on toes!

gerritbot added a comment.Nov 11 2025, 10:06 PM

Change #1204089 had a related patch set uploaded (by MusikAnimal; author: MusikAnimal):

[mediawiki/extensions/CommunityRequests@master] Render everything possible in the user interface language

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

gerritbot added a project: Patch-For-Review.Nov 11 2025, 10:06 PM
Samwilson reassigned this task from Samwilson to • MusikAnimal.Nov 11 2025, 10:44 PM

It's all yours! :)

• MusikAnimal changed the task status from Open to In Progress.Nov 13 2025, 12:09 AM
• MusikAnimal moved this task from In Development to Feedback and Review on the Community-Tech (Sea Lion Squad) board.
• MusikAnimal triaged this task as Medium priority.Nov 19 2025, 6:00 PM
• MusikAnimal set the point value for this task to 5.Nov 21 2025, 7:51 AM
HMonroy changed the task status from In Progress to Open.Dec 2 2025, 12:31 AM
HMonroy added subtasks: T407469: Voting success message close button on wrong side in RTL, T408880: Format tags field for MinT translation.
HMonroy moved this task from Feedback and Review to QA on the Community-Tech (Sea Lion Squad) board.
HMonroy changed the status of subtask T408880: Format tags field for MinT translation from In Progress to Open.
HMonroy changed the status of subtask T407469: Voting success message close button on wrong side in RTL from In Progress to Open.
gerritbot added a comment.Dec 2 2025, 7:02 AM

Change #1204089 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Render everything possible in the user interface language

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

jenkins-bot mentioned this in rECOR88ccdb56d8ff: Render everything possible in the user interface language.Dec 2 2025, 7:05 AM
Maintenance_bot removed a project: Patch-For-Review.Dec 2 2025, 7:30 AM
ReleaseTaggerBot added a project: MW-1.46-notes (1.46.0-wmf.7; 2025-12-16).Dec 2 2025, 8:00 AM
GMikesell-WMF changed the status of subtask T407469: Voting success message close button on wrong side in RTL from Open to In Progress.Dec 3 2025, 4:54 PM
GMikesell-WMF closed subtask T408880: Format tags field for MinT translation as Resolved.Dec 3 2025, 8:49 PM
gerritbot added a comment.Dec 5 2025, 10:35 PM

Change #1215721 had a related patch set uploaded (by HMonroy; author: HMonroy):

[mediawiki/extensions/CommunityRequests@master] Add user dismissable CSS class to cdx-message

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

gerritbot added a project: Patch-For-Review.Dec 5 2025, 10:35 PM
gerritbot added a comment.Dec 10 2025, 5:12 PM

Change #1215721 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Add user dismissable CSS class to cdx-message

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

jenkins-bot mentioned this in rECOR7bcf398d5078: Add user dismissable CSS class to cdx-message.Dec 10 2025, 5:13 PM
HMonroy changed the status of subtask T407469: Voting success message close button on wrong side in RTL from In Progress to Open.Dec 10 2025, 5:28 PM
Maintenance_bot removed a project: Patch-For-Review.Dec 10 2025, 5:30 PM
GMikesell-WMF closed subtask T407469: Voting success message close button on wrong side in RTL as Resolved.Dec 10 2025, 11:18 PM
GMikesell-WMF updated Other Assignee, added: GMikesell-WMF.Jan 5 2026, 7:46 PM
GMikesell-WMF updated the task description. (Show Details)
GMikesell-WMF added subscribers: HMonroy, dmaza, GMikesell-WMF.EditedJan 5 2026, 8:08 PM

@HMonroy @dmaza @Samwilson since MusikAnimal is away. Can you please review the below? Thanks!

Test Result - Meta Beta

Status: ❓Need More Info
Environment: Meta Beta
OS: macOS Tahoe 26.1
Browser: Chrome 143
Device: MBA
Emulated Device: NA

Test Artifact(s):

https://meta.wikimedia.beta.wmcloud.org/wiki/Community_Wishlist

Test Steps

Test Case 1: Display Focus Area Index in UI Language

Preconditions

  • The wishlist homepage is accessible.
  • The UI language is set to a language different from the wiki content language.
  1. Open Wikipedia.
  2. Change the UI language to a non-default language.
  3. Navigate to the wishlist homepage.
  4. Observe the focus area index section.
  5. ❌ AC1: Confirm that all focus area titles in the focus area index are displayed in the current UI language and not in the content language.

If the UI language is in Spanish, why is "Supported by: <# people> is in Spanish for all languages when you change the content language, except for English. Also when they UI is in Spansih "View 1 wish in this area" changes to the content language you select

Test Case 2: Display Wish Index in UI Language

Preconditions

  • Same as Test Case 1.
  1. Navigate to the wishlist homepage with the UI language set.
  2. Observe the list of wishes displayed in the wish index.
  3. ❓ AC2: Confirm that all wish titles and related textual elements in the wish index are displayed in the current UI language.

UI language as Spanish. I see that for the column headers, only "Status" translated to Spanish. Regarding information, only the dates in "Created" and "Status" are translated. What parts are supposed to be the UI language you select?

2026-01-05_12-01-16.png (851×1 px, 170 KB)

Test Case 3: Display Focus Area Filter Values in UI Language

Preconditions

  • Same as Test Case 1.
  • At least one focus area exists.
  1. Navigate to the wishlist homepage.
  2. Locate the focus area filter field.
  3. Open or interact with the focus area filter.
  4. Observe the focus area titles shown as selectable values.
  5. ❓ AC3: Confirm that focus area titles within the filter field are displayed in the current UI language and match the language of the filter label.

So only one header translated in the Filter Section. Also only the options in "Statuses" translated in Spanish. What parts in the Filter section should be translated?

❓ Possible Issues

What determines the FA card on the main wishlist page? I created a new one and it did not show. I also deleted the 2 FA cards that started with "856", but are still showing. If you want me to create any tasks from this, please let me know.

GMikesell-WMF changed the task status from Open to In Progress.Jan 5 2026, 8:09 PM
GMikesell-WMF updated the task description. (Show Details)
GMikesell-WMF moved this task from QA to In Development on the Community-Tech (Sea Lion Squad) board.
dmaza moved this task from In Development to QA on the Community-Tech (Sea Lion Squad) board.Jan 8 2026, 6:25 PM

@GMikesell-WMF Let me know if this is working as expected now after our discussion a few days ago

GMikesell-WMF added a comment.Tue, Jan 20, 6:12 PM

@dmaza Thanks for the info! Confirmed display all wishlist parts in the current UI language, as seen in the videos below. I will mark this as Resolved. Thanks for all your work!

Test Result - Meta Beta

Status: ✅ PASS
Environment: Meta Beta
OS: macOS Tahoe 26.2
Browser: Chrome 143
Device: MBA
Emulated Device: NA

Test Artifact(s):

https://meta.wikimedia.beta.wmcloud.org/wiki/Community_Wishlist

Test Steps

Test Case 1: Display Focus Area Index in UI Language

Preconditions

  • The wishlist homepage is accessible.
  • The UI language is set to a language different from the wiki content language.
  1. Open Wikipedia.
  2. Change the UI language to a non-default language.
  3. Navigate to the wishlist homepage.
  4. Observe the focus area index section.
  5. ✅ AC1: Confirm that all focus area titles in the focus area index are displayed in the current UI language and not in the content language.

Test Case 2: Display Wish Index in UI Language

Preconditions

  • Same as Test Case 1.
  1. Navigate to the wishlist homepage with the UI language set.
  2. Observe the list of wishes displayed in the wish index.
  3. ✅ AC2: Confirm that all wish titles and related textual elements in the wish index are displayed in the current UI language.

Test Case 3: Display Focus Area Filter Values in UI Language

Preconditions

  • Same as Test Case 1.
  • At least one focus area exists.
  1. Navigate to the wishlist homepage.
  2. Locate the focus area filter field.
  3. Open or interact with the focus area filter.
  4. Observe the focus area titles shown as selectable values.
  5. ✅ AC3: Confirm that focus area titles within the filter field are displayed in the current UI language and match the language of the filter label.

GMikesell-WMF closed this task as Resolved.Tue, Jan 20, 6:13 PM
GMikesell-WMF updated Other Assignee, removed: GMikesell-WMF.
GMikesell-WMF updated the task description. (Show Details)
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits