Steps to replicate the issue (include links if applicable):
- Go to https://en.m.wikipedia.org/wiki/Flotilla_(video_game)#
- Open the language selector
- Type Igbo
What happens?:
Error in the console.
listMatchedLanguageAutonyms ext.cx.entrypoints.languagesearcher.js:194
onLanguageMatch ext.cx.entrypoints.languagesearcher.js:236
showTranslationCTA ext.cx.entrypoints.languagesearcher.js:301
promise callback*showTranslationCTA ext.cx.entrypoints.languagesearcher.js:297
add mediawiki.base.js:534
js ext.cx.entrypoints.languagesearcher.js:306
js ext.cx.entrypoints.languagesearcher.js:308
runScript startup.js:1283
cssHandle startup.js:1351
flushCssBuffer startup.js:597
addEmbeddedCSS startup.js:628
execute startup.js:1365
doPropagation startup.js:748
requestIdleCallback handler*setAndPropagate startup.js:821
impl startup.js:2010
<anonymous> load.php:1What should have happened instead?:
No error should be displayed on the console.
Other information (browser name/version, screenshots, etc.):
Derived Requirement
Ensure that selecting any language (e.g., "Igbo") in the Content Translation language selector entrypoint does not result in a TypeError: cxLanguageMatches is null. The application must handle null or undefined values gracefully and prevent JavaScript errors from being logged in the browser console.
- The cxLanguageMatches variable must be properly checked for null before accessing its properties.
- Language selection should never crash the UI or throw console errors, regardless of the input.
Test Steps
Test Case 1: Ensure Language Selection Does Not Trigger Console Error
- Go to https://en.m.wikipedia.org/wiki/Flotilla_(video_game)#.
- Open the developer tools in the browser (Console tab).
- Open the language selector (translation entry point).
- Type Igbo in the selector's search input.
- ✅❓❌⬜ AC1: Confirm that no TypeError: cxLanguageMatches is null or similar JavaScript error is logged in the browser console.
QA Results - Test Wiki
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T389920#10722795 |

