Steps to replicate the issue (include links if applicable):
- Open an article available in only a few (or even just 1) languages on mobile
- Open the language selector
- Type a character that returns zero results in the search bar (e.g. "α")
What happens?:
A long list of language buttons appear that redirect the user to CX.
What should have happened instead?:
In previous ULS version (MobileFrontend LanguageSearcher) this entrypoint used a single card for CX entrypoint, so the final design of this entrypoint needs to be defined. Also, this entrypoint is not present on desktop.
Screencast from production el wiki:
QA plan:
- Follow the screencast steps on mobile
Acceptance criteria: Only two languages (plus ellipsis) are shown.
