Seems like a trivial change. Do we want to A/B this or just make it and compare before and after?

In T291286#7366218, @Jdlrobson wrote:

Seems like a trivial change. Do we want to A/B this or just make it and compare before and after?

We're expecting a large enough change to be able to see the before and after effects. That said, it would be interesting to A/B test in the future on a wiki that has not already seen the new version of the language switcher. Perhaps one of the wikis from T290091: Create logos and prepare new set of pilot wikis for deployment could be appropriate for an A/B test

@alexhollender - we will begin with a before/after comparison for the new button vs the old version of the button. Currently, this is blocked on receiving the updated data for changes since the first deployment.

@ovasileva I wonder if experimentation on the main page would make sense to include here...do you think it would be possible to include a title+language switcher on the main page of whatever wiki we're going to test the blue language button on, and also collect data on % of language switching from main page vs. article pages?

@alexhollender @ovasileva note about main page, there is a heading on all main pages by default. It's hidden by community members:
If you turn off styles you'll see it: https://en.wikipedia.org/wiki/Main_Page?safemode=1

We could edit the MediaWiki:Common.css page to reveal it on wiki for testing quite easily if that was wanted but that would likely need community buy in.

@sgrabarczuk - perhaps we can reach out to a few of the pilot wikis to see if they're interested in experimenting with the title.

In T291286#7441800, @Jdlrobson wrote:

@ovasileva it is okay if I assign you to the analysis? It doesn't look ready for an engineer to look at right now.

That sounds good - we're just waiting on some updated data on this one

Moving back to needs analysis. Based on the results in T294390: Analyze Language Switching Usage trend on anonymous users 3 months after new language button deployed, we will go forward with this change using the progressive version of the button. (cc @alexhollender)

Change 742997 had a related patch set uploaded (by Bernard Wang; author: Bernard Wang):

[mediawiki/skins/Vector@master] Make ULS in header progressive button

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

Hi all, I've just noticed this task for the first time (no surprise having all the focus and progress on Codex over last couple of weeks).
Late comments therefore: From a design system perspective the quiet progressive button with dropdown seems the preferable choice here.
The primary progressive button would be a wrong treatment as those buttons are aimed to signify the single, primary action in a view.

In T291286#7541977, @Volker_E wrote:

Hi all, I've just noticed this task for the first time (no surprise having all the focus and progress on Codex over last couple of weeks).
Late comments therefore: From a design system perspective the quiet progressive button with dropdown seems the preferable choice here.
The primary progressive button would be a wrong treatment as those buttons are aimed to signify the single, primary action in a view.

+1 to this take.

I also support the onboarding/user-education tooltip, and would suggest using the existing GuidedTour extension for this part.

In T291286#7541986, @RHo wrote:

In T291286#7541977, @Volker_E wrote:

Hi all, I've just noticed this task for the first time (no surprise having all the focus and progress on Codex over last couple of weeks).
Late comments therefore: From a design system perspective the quiet progressive button with dropdown seems the preferable choice here.
The primary progressive button would be a wrong treatment as those buttons are aimed to signify the single, primary action in a view.

+1 to this take.

I also support the onboarding/user-education tooltip, and would suggest using the existing GuidedTour extension for this part.

@RHo - I really like the guided tour idea for this! Do you know what the limitations are here? Does it show for every pageview? The main concern is that if we have it on for logged-out users we would like to avoid showing it on every pageview if possible.

In T291286#7550176, @ovasileva wrote:

In T291286#7541986, @RHo wrote:

In T291286#7541977, @Volker_E wrote:

Hi all, I've just noticed this task for the first time (no surprise having all the focus and progress on Codex over last couple of weeks).
Late comments therefore: From a design system perspective the quiet progressive button with dropdown seems the preferable choice here.
The primary progressive button would be a wrong treatment as those buttons are aimed to signify the single, primary action in a view.

+1 to this take.

I also support the onboarding/user-education tooltip, and would suggest using the existing GuidedTour extension for this part.

@RHo - I really like the guided tour idea for this! Do you know what the limitations are here? Does it show for every pageview? The main concern is that if we have it on for logged-out users we would like to avoid showing it on every pageview if possible.

@ovasileva GuidedTour uses cookies to keep track of which tours a user has seen. So if a logged-out user sees the tour and isn't using Private Browsing and doesn't switch browsers, they shouldn't see that tour again. Beyond that, when and where a tour is shown is something you have control over.

Test wiki created on Patch demo by Jdlrobson using patch(es) linked to this task:

https://patchdemo.wmflabs.org/wikis/a49fe25483/w/

In T291286#7555705, @kostajh wrote:

In T291286#7550176, @ovasileva wrote:

In T291286#7541986, @RHo wrote:

In T291286#7541977, @Volker_E wrote:

Hi all, I've just noticed this task for the first time (no surprise having all the focus and progress on Codex over last couple of weeks).
Late comments therefore: From a design system perspective the quiet progressive button with dropdown seems the preferable choice here.
The primary progressive button would be a wrong treatment as those buttons are aimed to signify the single, primary action in a view.

+1 to this take.

I also support the onboarding/user-education tooltip, and would suggest using the existing GuidedTour extension for this part.

@RHo - I really like the guided tour idea for this! Do you know what the limitations are here? Does it show for every pageview? The main concern is that if we have it on for logged-out users we would like to avoid showing it on every pageview if possible.

@ovasileva GuidedTour uses cookies to keep track of which tours a user has seen. So if a logged-out user sees the tour and isn't using Private Browsing and doesn't switch browsers, they shouldn't see that tour again. Beyond that, when and where a tour is shown is something you have control over.

Thanks for the info @kostajh, that will work for our use case! I've opened T297368: Add guided tour to improve discoverability of language switching functionality to track the implementation of the guided tour here.

In T291286#7558019, @Jdlrobson wrote:

@alexhollender: can you confirm https://patchdemo.wmflabs.org/wikis/a49fe25483/wiki/Spain?languageinheader=1&useskinversion=2 is the desired result here?

@Jdlrobson - I was discussing the analysis of the impact of these changes yesterday with @alexhollender and we determined that it would be best to be able to look at the impact of this change and the change introduced in T295555: Language switching: put an alert in the sidebar about where the language links are in isolation. Would it be possible to feature flag either/both of these?

Change 742997 merged by jenkins-bot:

[mediawiki/skins/Vector@master] Make ULS in header quiet progressive button

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

In T291286#7559363, @ovasileva wrote:

In T291286#7558019, @Jdlrobson wrote:

@alexhollender: can you confirm https://patchdemo.wmflabs.org/wikis/a49fe25483/wiki/Spain?languageinheader=1&useskinversion=2 is the desired result here?

@Jdlrobson - I was discussing the analysis of the impact of these changes yesterday with @alexhollender and we determined that it would be best to be able to look at the impact of this change and the change introduced in T295555: Language switching: put an alert in the sidebar about where the language links are in isolation. Would it be possible to feature flag either/both of these?

It's a bit late to add feature flags, but we can delay the merging of T295555 by moving it to blocked if that works.

Test wiki on Patch demo by Jdlrobson using patch(es) linked to this task was deleted:

https://patchdemo.wmflabs.org/wikis/a49fe25483/w/