This is not actually a real table of contents. This is injected by user content in the way of many of our TOC-like templates, making this a duplicate of T314254: Templates: CSS classes (toccolours, toc) related to TOC lost styling in Vector-2022.

This is just another case of T9356: User-specified HTML IDs can be the same as interface IDs.

In T380221#10825356, @STran wrote:

Are you looking up the IP of a registered user? As in, a registered user committed an action, CU logged the IP, and you searched for the IP via Special:Contributions? I don't think we've ever supported lookups for those.

Yes.

Issues with arbitrary onwiki Javascript are not tracked in Phabricator in general. It is found at en.wikt MediaWiki:Common.js line 226. You may followup at the talk page there.

Uh, it might not have existed then, but also I think I drped a bit there. inverted seems as fine as anything.

If I've sleuthed correctly in a non-English language, this template does not output a localized time because you did not ask for one in the parser function (see documentation). I can't say why it worked before, but that's probably one way to fix it now.

Since it's been mentioned, MediaWiki has established compatibility standards and I would encourage that they be read. "10 years and a dozen devices" is not how MediaWiki and by extension its ecosystem is supported.

Looks good now.

Then no, I just checked and this isn't resolved. This log entry is the relevant one.

I don't have a dev set up of any sort. I can look whenever this is live since it looks like the patches weren't backported, since I found this via an actual case onwiki.

I don't think I've ever used the calculator box when I've already got access to the IP/ranges actions. Where I've wanted a "copy IPs to calculator" button is on the get user IPs page, which will often list a ton of IPs, sometimes all in a nice range and sometimes not.

I have previously discussed something similar to this task with Krinkle at https://www.mediawiki.org/wiki/Topic:Tvju6hdstykonsbj (section title "Process to change compatibility" on Talk:Compatibility for if/when Flow dies on MW wiki). I don't know if Krinkle ever followed up on that discussion as they suggested they would.

This is not a problem with the wiki software. You need to configure your installation of the templates to support the date formats that you allow. You can request further assistance at https://en.wikipedia.org/wiki/Help_talk:CS1 .

Misnested lint hits wrong close order of tags and sometimes block in inline tags (in old terms).

Guessing this is CampaignEvents

The global terms should be preferred for i18n purposes. That said, I'd rewrite the note as "Filters can now be set to suppress attempted edits and actions [automatically]." which avoids the issue. Link suppress to the relevant MW wiki documentation page or Wikidata item, and add a separate "see filters documentation about this feature" sentence after, wherever that lives.

The correct place to document extensions adding Lua functionality is on their extension pages, potentially with a pointer from section extension libraries.

The linked task seems to have decided that it's basically stable, recommending it officially for use, pointing out the mechanism for its use is over 10 years old... so, that response doesn't jive with the reality.

In T395028#10851191, @Bugreporter2 wrote:

But if "the point of the extension in fact is to provide for demand that already exists on Phab and elsewhere," then it should be merged, no?

I have filed T395079 about one of these recommendations.

I don't think this makes sense. Several of these CSS blobs are implemented and others already have their own tasks. The point of the extension in fact is to provide for demand that already exists on Phab and elsewhere.

The only systems I know that will actually prevent a save of a wikitext content model page are associated with the edit filter or a blacklist (see also T279275), not the linter extension.

Is this complete?

I would categorically prefer a task like this to be implemented and have previously argued it when discussion of category templates was at hand (perhaps not on Phab?). Categories are almost always going to be a middleman in the context of these kinds of limited gadgets, and all the category gadgets on enwiki are closely associated to a handful of templates.

/testcases too if it isn't already hidden.

This seems to have caused this discussion on en.wp also.

Indeed enwiki.

I can observe at least one IPv6 address which has 14 hits in the CU database which displays

Assuming you have CM6 enabled, this was changed circa August 9 (date based on a discussion in Discord) when the new search bar was implemented in T371436: Redesign CodeMirror search panel. Apparently it's related to performance. I pinged you to the discussion on Discord.

Can we please get some version of the report publicized?

Think this may be due to the work that WMDE has been doing on the Cite module, and I suspect that the app has custom CSS that was forked there at some point that needs review.

This is a problem on Discord's end. Appropriate OpenGraph metadata is provided. The canonical URL is also appropriately identified. Yes, they have some hack in place that doesn't believe that's the correct page with a slash in it, and it's been well known for ages. It affects other pages, as was explained to you on Discord just before you filed this task.

In T392966#10778956, @kostajh wrote:

In T392966#10778939, @kostajh wrote:

In T392966#10778911, @Johannnes89 wrote:

Agree with Izno. But I can reproduce the slow loading time for IPs in https://en.wikipedia.org/wiki/Special:AbuseLog?wpSearchUser=&wpSearchPeriodStart=&wpSearchPeriodEnd=&wpSearchTitle=&wpSearchImpact=2&wpSearchAction=edit&wpSearchActionTaken=&wpSearchEntries=0&wpSearchFilter= without actual edits, took 5-30 seconds checking different IPs, while the IP inbox loads right away for random IPs with valid edits.

I can reproduce that (but probably needs a separate task, which I can file a bit later). Example profile data https://performance.wikimedia.org/xhgui/run/view?id=6811c05e0d7e3f4c23c47f2b

Filed as T392976.

Then you probably found the correct place to request assistance.

This is expected, see T380221: Allow authorised users to see IP Info for actors if the IP exists in the CheckUser or AbuseFilter tables, or has contributions.

This should be reported downstream at https://meta.miraheze.org/wiki/Phorge .

I've said it on Discord, but the whole block progression (including appeals) is something that is ripe for a Flow-esque aspiration (search "appeal" from me from January 2025 and also from October 2024).

In T392755#10770364, @Aklapper wrote:

If a page has teh __DISAMBIG__ magic word, it shouldn't be counted as an article.

I don't see why.

Verify that this doesn't break on Minerva, which has opinions about the sizing of images that doesn't play nice with flex / tables necessarily. (IDK if this error displays in Minerva.)

In T392330#10767132, @Bugreporter2 wrote:

Wrapping everything in <syntaxhighlight lang=json> makes a completely incoherent neon-coloured headache-inducing mess. There is no lang=regex option, but there are, at least, other language options that aren't quite as bad.

In T337431#9541677, @matej_suchanek wrote:

Unlike BlockedExternalDomains in its current shape, SpamBlacklist checks edit summaries for spam, too (T15599#173812, code snippet: T296102#9534553).

And using a JSON content model as in the new BlockedDomains would likely highlight regexes appropriately anyway. So yes, I more or less agree with that suggestion regarding the context of the spam blacklist.

global search has a few more uses that may cause spam outside dev console.

In T270984#10755044, @Alien333 wrote:

@Izno : On the bar graph display, is it T311704 (the bars being squished together) or something else?

I would suggest forking the spam related content to a new task to be a child of T337431: Rework MediaWiki:SpamBlacklist and this task.

The way to fix this issue is to assign data-sort-value to each table cell you wish to have a specific sort order. See https://en.wikipedia.org/wiki/Help:Sortable_tables#Specifying_a_sort_key_for_a_cell This is because the cells at issue are not seen to be numeric because of the < character.

In T391926#10742409, @Bugreporter wrote:

We should wait until T373711: Add support for Scribunto, JavaScript, CSS, JSON and Vue to CodeMirror 6 is resolved. There is no reason to bundle both CodeEditor and CodeMirror.