I can produce something like this description if I have just the right (or wrong?) combination of font and screen sizes in Chrome on macOS. It looks a little weirder with a different tab selected, e.g., when the editing window is open.) I think I could manage this on old Vector as well, but I don't have a screenshot of that.

That's right: There were no objections, either before the test started or after it began.

I'm pretty sure that I've also heard this complaint at the English Wikipedia more than once.

To clarify:

Given the low opt-out rate for the [reply] tool, I'm not sure that we should have an in-tool opt-out affordance. It's possible that more people would accidentally click it, and then wonder why a favorite feature disappeared unexpectedly, than would value it. Perhaps this ticket should just be closed?

@ppelberg, we have https://www.mediawiki.org/wiki/Help:DiscussionTools Is that enough, or did you want to add something more?

Update on timing: Phase 1 and 2 are done. Phase 3 will probably happen the first week of June. From there, deployments could proceed at a rate of one deployment per week.

Also, if you can do this, then when I haven't added a section heading anywhere, could you make the error a little more intrusive? I had to go back and fix two or three such messages on the same afternoon recently.

Fully translated into 13 languages at the time it was very kindly sent by @Quiddity

This is about half done, with the ko, bn, and vi (the ones we need now) done and the rest requested (some started).

I think this happens with all of VisualEditor (not just its 2017 wikitext mode), and I think there is an old bug report that this is essentially a duplicate of. See also https://www.mediawiki.org/wiki/Topic:Wtrv8ofa4cyllouc for a bug report that has nothing to do with Extension:Translate, but which is the same kind of problem in the end.

This could also be useful for the Wiktionaries: https://www.mediawiki.org/wiki/Topic:Wtrrpeiugakj6ykj

In T297520#7730214, @Nux wrote:

They just expect a "Save" button and cannot find it.

I have some notes on this at https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox2&oldid=5090122 in case anyone wants to play around with it.

There are more features to show, so we're going to re-write the landing page and advertise this in bnwiki, kowiki, and vi.wiki next.

The "Topic containers" requires these three messages in each language (two of which have plural options):

I've requested translations of mw:Help:Sample discussion via https://www.mediawiki.org/wiki/Special:NotifyTranslators for fr, he, ja, ko, vi, and zh. We already have bn (and ar) translations for that page. Getting the translated sample page out of mw.org and into Patchdemo is probably going to take about an hour per page, mostly because the time stamps have to be changed so that they match whatever the local time is for the wiki that we're using.

We're going to re-write this page before we request translations.

looking at the time between someone publishes a new topic or a comment on a talk page and someone else posts a response to said new topic or comment.

I'm not sure that I understand the "receive quicker responses" idea. Here's what happens:

Sam, I know there's a fair bit of code touching this, but as a simple start, do you want to turn off the visual editor in the relevant namespaces? That's a simple config change, and it should stop people from accidentally using it.

Note for anyone trying to do something similar in the future: If the wiki's "content language" is (for example) Arabic, then the Arabic translation goes at the "main" name, not at the usual /ar subpage.

Based on a convenience sample of whichever of my teammates replied first, the second (broader) banner was preferred 3:1 over the first (specific) option.

In the discussion at https://www.mediawiki.org/wiki/Topic:Wq2ekwwt65nu3mp2 Valereee has suggested making the warnings about edit conflicts be opt-in, and specifically that they be turned off for new editors. The benefit to new editors (<100 edits, so 99% of accounts?) is likely to be much lower, and the anxiety about what's going on (did I break something? Am I doing this wrong?) is likely to be higher.

Peter, I like this simpler language. It would be possible to shorten the sentences (e.g., "Help improve talk pages. Share feedback...") but I don't think it is necessary to do so.

I've added three strings to a test-Patch-Demo site. They seem to work, but I need @Dyolf77_WMF or another Arabic speaker to figure out if I did it correctly.

The opposite of this (force the reply tool to appear, even if it's in the "wrong" namespace) has also been requested.

I've started a basic talk page at https://www.mediawiki.org/wiki/Help:Sample_discussion Once it seems like it covers everything we need, then we can translate it. The extracted copies (in whole or in part) can be pasted anywhere we want to test.

See also:

We will need:

• a CentralNotice banner campaign
• a landing page at mw.org
• a PatchDemo site
  • with the new UI elements available in the target language

2022-02-02T18:51:00.000Z is easier to recognize as containing a date than 20220202185100. 2022-02-02T18:51 would be even easier.