Change 807073 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/skins/Vector@master] Show ULS button when article exist only in single language

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

In https://gerrit.wikimedia.org/r/807073, Vector skin is modified to show the language button even if article has only one language.
{F35259030 size=full}

Now we need to change the ULS to respond to that state with the design outlined in this ticket.

@Pginer-WMF In the empty state we should avoid the entrypoint we injected from CX right? - the top "Missing in x, y and more" entrypoint?

@Pginer-WMF In this design, the message " You can translate this page, or connect..." depends on whether we have CX/SX entry point or wikidata entrypoint. But ULS will now know about these entrypoints. ULS does not add them. The extensions like CX or wikidata inject these entrypoints based on defined in conditions in them. This is how the action items is registered. So constructing this message at the side of ULS is not easy. May be translate entypoint is present, but not wikidata. or vice-verse.

Is there a generic message we can provide without tightly coupled with the entrypoints that are added by other extensions? If required we can make sure the entrypoints from CX or wikidata also provide a brief message on what it does. Example: {label: "Translate this page" , description: "You can translate this page to another language with the help of translation tool"}

Change 807929 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/extensions/UniversalLanguageSelector@master] Add support for empty states to the current language selector

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

In T290436#8022390, @santhosh wrote:

Is there a generic message we can provide without tightly coupled with the entrypoints that are added by other extensions? If required we can make sure the entrypoints from CX or wikidata also provide a brief message on what it does. Example: {label: "Translate this page" , description: "You can translate this page to another language with the help of translation tool"}

Thanks for surfacing this. I can see the complexity that extensibility brings here.
I think wha we can assume is that extensions will provide ways to expand the list of languages. So for this case we can consider:

No languages yet. Add a new one?
Make the content available in more languages.

This is a bit more encouraging than the default message used when no additional options are available (No languages yet. No languages are available for now.) while still being general enough to cover the cases of Wikidata linking, translation or other future mechanisms of contribution for the list of languages.

Is this a more feasible approach?

In T290436#8022281, @santhosh wrote:

@Pginer-WMF In the empty state we should avoid the entrypoint we injected from CX right? - the top "Missing in x, y and more" entrypoint?

Yes. I think we can skip it to avoid multiple messages that overlap conceptually. Here we already mentioned that the page is missing in all (other) languages.

Change 809917 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/extensions/ContentTranslation@master] relevantlanguages entrypoint: Hide if no languages

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

Change 809917 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] relevantlanguages entrypoint: Hide if no languages

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

Change 807929 merged by jenkins-bot:

[mediawiki/extensions/UniversalLanguageSelector@master] Add support for empty states to the current language selector

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

Change 807073 merged by jenkins-bot:

[mediawiki/skins/Vector@master] Show ULS button when article exist only in single language

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

using the article https://en.wikipedia.org/wiki/Ndowa_Lale as stated the "Edit Language Links" is not available

Also there is a search message highlighted below in the image

In another article : https://en.wikipedia.org/wiki/Ndawa the search message is missing as shown in the image below:

@santhosh are they both expected in different situations ? and if so what situations are they ?

In T290436#8216494, @EChukwukere-WMF wrote:

using the article https://en.wikipedia.org/wiki/Ndowa_Lale as stated the "Edit Language Links" is not available

The actions in the selector when "Add languages" are shown are plugins. Meaning, they comes from various extensions. Wikidata is yet to add the "Edit Language Links", so it is not available yet. It is tracked in T310259

Also there is a search message highlighted below in the image

In another article : https://en.wikipedia.org/wiki/Ndawa the search message is missing as shown in the image below:

@santhosh are they both expected in different situations ? and if so what situations are they ?

The search message at bottom appears after a search. User type something in search box. Till that happens that message is not shown

@santhosh thanks for the clairification, I see the message now and it makes sense.

I will move this to done

The ticket has two parts:

No initial languages
This section seems to be complete with a ticket proposed for covering special cases: T316559: Communicate when pages are not supported in other languages in the current language selector

Searching a language that does not exist or content is not available
This part does not seem to be supported yet:

@Pginer-WMF, I have a question related to the case "Searching a language that does not exist"

As per the ticket , we need to customize the no-language experience like this:

And the current behavior is as follows

Technical note after a quick exploration: Implementing custom "no-results-for-search" screen is tricky. jQueyr.ULS accepts an option to pass a function that builds this screen. But that option is already used by mediawiki ULS customization. Overriding that option by another mediawiki extension(CX) is not possible right now. Unless we make MW ULS aware that other MW extensions can customize it - That is too much fragility we are introducing. The behavior will depend which extension registers the "no-results-for-search" first.

@Pginer-WMF, do you think leaving it as current behavior and not adding this complexity is an acceptable trade off?

I can also think of some other solution - which is definitely hacky - Render the expected screen always, but hidden. Then use a CSS selector to hide it or show it based on the ULS dialog has a class uls-no-results

In general it is high time that we rethink about entrypoint mechanism and next gen ULS that can accommodate these needs without getting into this hacks

In T290436#8258761, @santhosh wrote:

@Pginer-WMF, do you think leaving it as current behavior and not adding this complexity is an acceptable trade off?

Thanks for all the context, Santhosh. Given the technical complexity, I think we can skip that part for now and consider it for the new version of the selector.

Based on the preliminary entry point results (T295757#8256279): on mobile 16% of users were reaching the tool through this empty state after they searched for their language. One simple way to provide some support for this case on desktop is to leave the "Missing in X, Y, and more" visible in this case (as it is the current state). Even if we remove this invite when searching (which was not intended to be seen in such context) it may be good to keep it for the empty state.