Currently, Hindi doesn't have V22 as the default, though.

How about a special character not used for wikitext formatting? for example ^?

Thanks for your message @Aklapper. I think we could take next steps within the Web team nevertheless. Patafisik is our ambassador, and making progress with this may legitimately be beyond her expertise.

Feedback from @Kipod

Same.

1. Can't reproduce
2. Can reproduce

I've removed this from the descriptions of my regular duties (both the team page on Meta and the internal table). Last calendar year, unless I'm mistaken, we did this 0 times. To me, it looks like this: should our team receive any request, either Benoît or I will react. But in terms of regular workflows and time allocation, it's been 0%-ish.

Ideally, shouldn't this be the main action item in the main namespace across all Wikisources for all logged-out users, something displayed next to/instead of Edit, but stronger than that?

Thanks @abi_! Unfortunately, I've just experienced this ↓ on MediaWiki.org when trying to mark this page for translation:

@alexhollender_WMF FYI

Hi @Iniquity. This is about enwiki only because now, we're focusing on enwiki. We're making plans on when to approach the remainder of large wikis, incl. ruwiki, with the direct question about the deployment as the default. Before we initiate such discussions, we'll put up banners encouraging active people to opt in voluntarily on an individual basis. The numbers will change significantly. I presume that in the messages opening the discussions, we'll share the statistics.

When I add safemode=1 to the URL, the menu works as expected. So the issue must be due to some incompatibility with a gadget turned on by default for everyone/all logged-in users.

Sure, but let's continue the discussion on that separately to keep this task just about the bug. I'll reach out to you.

It's working. Thank you!

@Volans, I need access to the Desktop Improvements dashboards/statistics in Superset. This requires access to private data.

Volunteers helped me to find the reason why I had experienced this. This is now fixed. Thank you everyone!

I think this may be resolved, we'll make decisions about the future usage of the banners separately.

This will never end.

Let me add another complication - in principle, because of accessibility, colors shouldn't be used as the only visual means of conveying information[source]. So we could ask editors to change the way they design infoboxes, navboxes, tables. It'd be ambitious, it'd be great, and we might've (I'm not sure, really) never ever done anything about this successfully.

That task was about lower resolutions, and here I've shared shots of my 2560px-wide screen. So I presume it's not intended.

I've added a line

mw.track('counter.MediaWiki.vector_banner_signup');

to the banners suggesting some logged-in users to opt-in (T304839).

I've set up the first banner (incentivizing to opt-in). Settings:

• Only logged-in desktop legacy Vector users with less than 500 edits
  • In the calendar, I wrote that we may target more experienced users at some point. It may be necessary for the communities to prepare for the deployment.
• Start and end dates: May 12-19
  • In the calendar, I wrote that the full time frame is May 11 (when I tested the banners) - June 15. This was to inform everyone working on CentralNotice that we may set up the banners after May 19.
• Languages: all wikis where a given user has any of these languages set up (either as the default or due to their own choice) as the interface language. So if a user has the English interface on Spanish Wikipedia, they'll see a banner in English.
  • I set up the banners for more languages when the translations are added. Initially, the banners were only set up for English and Polish, then I added more. I'm waiting for more translations.
  • I also add some languages of the largest wikis where any of those ^ languages are the fallback languages. So when I have the Portuguese translation, banners in Portuguese will be displayed on Galician Wikipedia (#79 in December 2021).
• Limits:
  • Impression diet: a user can see our banners up to five times per cycle (which I've set up to be one week). After that, the cycle restarts. This is a standard setting for the Community Wishlist Survey banners.
  • Traffic limit (initially): 10% for Wikipedias with English interface (that's mainly English Wikipedia), 33% for non-Wikipedia projects with English interface, 50% for all wikis with non-English interface.
  • If the number of opt-ins is clearly too low, I may increase the limits (number of impressions per cycle and traffic limits). I'll ask other CentralNotice admins what thresholds would be reasonable. We need not to interfere with other banners.

One of the goals for introducing the limited width was Establishing a common reading experience. Bearing that in mind, I'd like to suggest - let's maybe consider making the editor window appear in full width while keeping the non-live preview above it in limited width?

Note that I don't want to pick on words.

We appreciate that :D

it would actually be good if they are distracted with ways to contribute. Readers should want to fix things. Should know they can fix things. Should know they can ask to fix things. Should know they can ask for help. It is not a distraction. It should be one of the goals. We need fresh blood all the time

Absolutely right! This is part of our basic flywheel (find content -> view it -> edit and provide more better content -> find -> ...). We work closely with Growth and Editing to ensure that our changes are integral. Together, we plan on making the entry points to the community properly exposed in the interface (that's our part) and effective (that's Growth's part). That's the general approach.

"Vector" is definitely too technical. Also, it is recommended (by CN admins) to put between 50 and 70 characters.

Yeah, right now, there's no easy way to find our project page or project talk page, which is becoming an issue, since more individuals and communities do/are going to have Vector 2022 as default.

@Patriccck, the A/B test will only be performed on the early adopter (test) wikis. As I can see, you mostly edit Czech Wikipedia, which is not on that list yet.