Kind of related is T272376 which lets the mentor resign from mentorship and re-assign mentees to other mentors. T272376 is a mass opt-out effectively.

AFAIK you should be able to tell which editor is open from CSS classes. At least with VE you get ve-active on html tag. Plain editor is both for action-submit and action-edit (on body) which makes things a bit weird as it is almost the same view.

Also note that T284921 talks about numbers in HTML and a lot of users says that probably the numbers should be kept for headers but implemented with CSS.

This is not the same. T284921 says:

The "auto-number headings" controls whether section numbers are shown in section headings. The default behavior is to show numbering in the table of contents, but not in the actual section headings.
Solution:
If there is no great demand for this feature, we should simply remove it. If the feature is to be kept, it should be implemented in CSS: the numbering would always be generated, but the browser would be instructed to not display them. Appropriate CSS rules for showing the numbers could easily be generated from the user settings on the fly. Numbering in ToC would remain

Also note that the menu is not working.

I love how the new sidebar design works with new tabs design :-). I saw those tabs on Tar's presentation on Polish Wzlot and I really like them. And now I also like the new menu :-)

Kind of a separate issue, but probably with the same root cause (layout problems).

Nevermind. Forgot I can change that ;-)

You should probably add port mapping info in troubleshooting: https://www.mediawiki.org/wiki/Extension:VisualEditor#Troubleshooting

Sorry. I haven't noticed this used to work and was reverted. https://gerrit.wikimedia.org/r/c/mediawiki/core/+/478734/1/resources/src/jquery/jquery.textSelection.js

@Pols12 You can repeat the steps in any browser. You just have to disable syntax-highlighting. The problem is that functions inserting text don't use document.execCommand which was mentioned by Jack.

Also added a prototype for plwiki here: https://commons.wikimedia.org/wiki/File:Oznacz_wersj%C4%99_mobiliki_prototyp_plwiki.png

If you open a diff, I’d expect you to be interested in the diff, not the rendered content, so I don’t see any reason to collapse the thing that you’re most interested in.

1. Open [[Special:PendingChanges]].
2. Go to some un-reviewd article. E.g. now: https://pl.m.wikipedia.org/wiki/AXN_Black

Maybe you could incorporate this list into citoid and use it to ignore url replacement at least. Because Bloomber is also replacing url with fake url. Once you do automatic generation you have to find the correct url again.
https://www.bloomberg.com/tosv2.html?vid=&uuid=8c153f6a-955e-11ec-b858-6c5a6b626661&url=L25ld3MvZmVhdHVyZXMvMjAxOS0xMi0wMy9tZXJjay1jeWJlcmF0dGFjay1zLTEtMy1iaWxsaW9uLXF1ZXN0aW9uLXdhcy1pdC1hbi1hY3Qtb2Ytd2Fy

Here is a user story from today (I'm translating from Polish):

For what it's worth I've reviewed this and I think this patch can be applied. It's a simple patch. At worst it might not work for all cases, but will at least be better. Could someone merge this? Thanks.

I've checked that 2022 is loaded https://pl.wikipedia.org/wiki/MediaWiki:Vector-2022.js

In that case preferences page is misleading. I have a link to [[User:Nux/vector-2022.js]].

Both User:Nux/vector-2022.js and User:Nux/vector.js will be loaded. Yes the preferences is a little confusing, but I'm not 100% sure how to fix that or if it's worth fixing at the current point in time since this is temporary behaviour.

OK, that probably won't cause immediate problems...

No changes necessary here. Both Vector skins will load User:<username>/vector.(css|js).

Is this a one-time only change? Or should we expect for this trend to continue in the future? I'm wondering how to modify gadgets (add a new string to if/switch or change to prefix-check).

Note that this also affects templates. You cannot edit any template within a list, at least not with a mouse. Same problem with touch screen.

Hm... Hi there. I was quoted on top 🙂, so two things:

I'm not sure, but I think this probably means we need to provide a way to set position = top on user scripts. Maybe it is related to the need of creating modules from wikipages, maybe not.

I actually do not need that as much any more. I use Stylus (a browser extension) if I want to make some changes quick. Also browsers are much faster then 10 years ago so that flickering effect when css is added is not as much as of a problem as back then. So AFAIK that part alone is probably not a big deal any more.

I think you should consider using PWA instead of using localStorage. As you probably know localStorage has size constraints based on base domain (based on wikipedia.org, not en.wikipedia.org). So data might overflow and be removed for users visiting many language versions. I guess you might have handled it somehow, but service worker using cache API would be better in any case. Shouldn't be too hard to do. You could also do it in steps (e.g. migrate only SCM scripts and css to PWA). See also:
https://enux.pl/article/en/2018-05-05/pwa-and-http-caching?language=en

Cool feature 🙂,
but I keep getting "You have been subscribed".

@thiemowmde Yeah, I can understand that need, but that would require much more work from wikimedians (reconfiguring templates manually). There are also more complicated cases were parameters e.g. for images should actually be grouped and both removed as a group and added as a group... So maybe something for a different task? Both mechanism could work together.

Hi. Following a vote, I made a patch/override to keep empty parameters for infoboxes on plwiki. This is now live on plwiki (also for IPs).

Hi. So few months later... Any chances on applying this fix on the toolserver?

Would be nice if tool author could somehow take ownership of the tool and be able to clean up and edit details of the tool.

How about using namespace to pass on extra attributes to a template in the ref?

Definition:
<ref name="Test">{{Cite|title=Test|page=50}}</ref>

Just FYI added a workaround in WP:SK too. But I guess this might be a problem on other wikis too.

You can find browser versions and features in Kangax tables (at least a few versions back):
http://kangax.github.io/compat-table/es2016plus/

The border seems to be still on your screen (marked it in red):

Note that in all of your examples with arrows the arrows are pointing right or are not in the left corner.

Maybe you could just use the same icon for both states? I would be happy with that and alignment is OK too 🙂 (with above css).

Yeah, there is a Github repo of the tool (the php one), but there is a pull request there from March 2020... So I would say an update from the original authors is not likely.

Here are some more menu icons along with animated state changes: https://jonsuh.com/hamburgers/
Personally I think minus [-] is better then [X], but if "menu" word would be added then both would work fine I guess.

How?

With a mouse wheel.

No, this is for all pages that go full width (special-special pages being one of them though). So also the Growth project user page like this one:

Well it is a menu. A menu that comes from the side, but still a menu. And yes I know hamburger icon is bad and you shouldn't really use it... But it was/is already there in new vector design. So I'm not going to contemplate that. You can find great work about that from Luke Wroblewski if you want.

In T280078#7051257, @matmarex wrote:

I don't think that solves the problem though. We still need to distinguish two kinds of suggested parameters – those that should be added to the wikitext even with no value, and those that should not.

Hi. We have quite a lot of broken scripts on pl.wiki. I've fixed some gadgets yesterday.

We just had this problem on Polish Wikipedia. A mentor does not have time to answer questions anymore and wants to quit. He removed himself from the list of mentors. But the problem is that he still gets questions.

As a reference: Possibility to remove required params was explicitly blocked in T62358.

You mentioned removing templates so I assumed that would be part of the process of moving coordinates to MediaWiki. From a programmers stand point that's how I would do that 😉... Don't know how you would want to do that otherwise.

Also note that coordinates in the template influence not only the top bar, but also contents of an infobox. Not sure if that's what you meant by saying: "Sometimes the location of the coordinates is defined on multiple places on the page."... But I want to stress that this is not just display of coordinates. They are shown on maps as well.

You seem to have forgotten that the coordinates are NOT ONLY a simple link. On Polish Wikipedia we open up a map that shows placement of the object/POI that article describes.

So assuming you don't like the structure of this: https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram/1.34.0&action=edit

Don't know about other wikis, but on Polish Wikipedia the ui admin is someone with technical knowledge and technical abilities. Sysop is someone doing moderator work. Which has some requirements of being active etc. We actually had a long debate befor ui admin that this should be something available for technical people that don't need to or don't have time to sit on RC etc.

Relatedly, we've talked a bit about how it might make more sense for the page title to be above the tabs (instead of below).

Oh. Note that the area on the right side of title is already used by various icons and maps. Not sure how many wikis have such things but Polish Wikipedia have this for ages.

Looking at the article history of an article in German Wikipedia I realise it's got to be imported from English. I don't want to comb through the history to find the link to the English article, it's quicker to just click on the language link. But, uh, it's not there? Oh. I have to go to the article tab first.

Hi, Roan. I think a slightly longer version is a good idea 🙂.

We don't have a separate tutorial or a page about updating articles. Are these blockers?

The Homepage suggests to users to read a page that explains what Wikipedia is and how it works. Any page is fine, as far as it is not cal for action (like https://pl.wikipedia.org/wiki/Pomoc:Pierwsze_kroki does).

Tutorial (Q915263) -- this seems wrong. It links to a historical tutorial.

Manual of style (Q4994848): https://pl.wikipedia.org/wiki/Pomoc:Styl_%E2%80%93_poradnik_dla_autor%C3%B3w. More or less... We don't have such a large compendium as enwiki, but should be enough for beginners.