@Krinkle, is it possible to make deprecation "noisy"? Even when script owners are personally informed about upcoming changes with messages on their primary user talk pages, or messages are posted in their native language to the official page for that wiki's gadgets, scripts don't always get fixed until they break. So instead of trusting the deprecation notices from the web browser, could we have a little box, similar to the "Your edit was published" toast, that says "You're running a script that will break soon"?

1. The things I really care about are already present.

That last diff (Roman Sondermajer) looks like a different "problem", namely that the editor manually created a basic citation. There's no template substing going on in any of these (see this edit to find out what happens when you subst a CS1 template), but the 4 October 2019 example doesn't look like a software problem at all.

Yes! It's fixed for me!

Are you trying to do something like what @Reedy did with AWB in T111663: Tag AWB edits? Also, I think ProveIt is on the list at T185382: Add manual tag- messages to Wikimedia Messages for common tools/gadgets.

Notes are here: https://etherpad.wikimedia.org/p/tpc2019

I imagine "Citation needed" and "Edit template" won't fit on one line in German

@I_JethroBT: Do you have any recommendations for Japanese?

I think that https://www.mediawiki.org/wiki/Topic:V6bd8m6687tc4ta9 by User:Pelagic is a similar problem, but it appears to only be in some versions of iOS.

The mobile visual editor has a checkbox for minor edits. The mobile wikitext editor does not. @ppelberg, should the VisualEditor tag be removed from this task, and the description updated to specify that the problem is in the wikitext editor?

This is going to need a help page, the main purpose of which is to explain to local admins how to identify these templates at each local wiki.

Also in a Chrome incognito window while logged in to https://en.wikipedia.org/wiki/User:WhatamIdoing-test

I can reproduce this, in plain vanilla Chrome Version 75.0.3770.142 (Official Build) (64-bit) in my staff account, and in Firefox Quantum 67.0.4 (64-bit) in my volunteer account, but not in Safari.

Posted at https://www.mediawiki.org/wiki/Talk_pages_consultation_2019/Phase_2_report

{{done}}

Ilana, I'll ping the participants. We should ping everyone, not just the supporters.

• Show me how you work! (Just let me look over your shoulder while you do whatever you would normally do.)
• Please try out the Edit Cards and Toolbar Refresh on mobile visual editor.
• Please try out the visual editor. Lots of experienced editors haven't looked at it since 2013 or 2014, and are just amazed at its abilities. Suggest that they try deleting a column in a large wiki table. :-)

With thanks to @Trizek-WMF for doing the delivery work.

See also https://www.mediawiki.org/wiki/Structured_profiles

My account at nlwiki was created on 15 July 2013.

It sounds like we should be talking to @Catrope about this.

I don't expect to make any progress on this any time soon. However, if anyone wants to do this and has questions, please feel free to leave a message for me at http://mediawiki.org/wiki/User_talk:Whatamidoing_(WMF)

Saving dozens of tabs and restarting Safari seems to have solved the problem. Or perhaps it went away for unrelated reasons.

Thanks

First pass completed on Thursday morning.

I think we're done with this stage of this project.

They'll want to know when to expect the changes, but I think we're in good shape.

I can indeed edit the lead section at enwiki, on the mobile site, with JavaScript disabled.

Recommendations have been sent to the Editing team's mailing list.

Be me? I was editing on office.wiki, so that means Safari version 12.1 (14607.1.40.1.4) on macOS Mojave 10.14.4 (18E226). I think that changing the screen size resolved it. Also, sometimes when the toolbar was in the right place, the drop-down to switch editing modes was detached. I assume that was related.

Thanks!

https://www.mediawiki.org/wiki/VisualEditor_on_mobile/Usability_improvements was reviewed and improved last Friday. We can consider that project page {{done}}.

This is great news. Reducing the number of systems down to two will make writing the user guide easier.

So we'll end up with two systems:

We have three systems: