I find the placement of the lightbulb indicator in the top right blocks the reading of the edit pencil and/or makes it look like it is part of the edit pencil:

https://www.mediawiki.org/wiki/Citoid/Enabling_Citoid_on_your_wiki#Step_2.c:_Configuring_a_special_MediaWiki_message

FWIW for the biggest and most obvious case listed here, French, I'm not aware of complaints from frwiki about the lack of space before the :, nor proposals to add it (an on-wiki CSS fix would be trivial).

In T315893#12128387, @doctaxon wrote:

You must know that it's indeed not a language issue or an orthography issue, to put a space behind the colon. We are not talking about sentences or word terms in any language. We are talking about namespaces and page titles, that are bound to a string by a colon. So it's not advisable to change anything to something that looks like colon-space with the intention to correctify a language-based issue.

@SD0001 Filed as T432346

Given the lack of requests for translating the separator I don't think that is a priority for now, and while our APIs are mostly tolerant of additional whitespace, they would not handle different separators so it would be a vastly more complicated undertaking and beyond the scope of this task.

And you cannot easily disable this enhancement while keeping all the other ones, so that point is moot.

A global vote would make sense because this is a global change that was not consulted about with any language community.

For enwiki at least, this changes applies to ~76% of namespace prefixed pages. I'd like to get this to the remaining 24%. The main issue is that the current feature and preference lives in DiscussionTools, so we need to:

• Move the feature to core
• Create a core preference that is initially disabled for anyone who has DT visual enhancements disabled.

I can still reproduce in the sandbox

Now that ResourceLoader has sourcemaps, and Chrome V8 reports coverage, this should be feasible.

In T304753#12119066, @Esanders wrote:

The current logic means enhancements are available on most talk pages, and can be added to more with __NEWSECTIONLINK__ (excluding the main namespace):

// Visual enhancements are only enabled on talk namespaces (T325417) ...
return $title->isTalkPage() || (
	// ... or __NEWSECTIONLINK__ (T331635) or __ARCHIVEDTALK__ (T374198) pages
	(
		static::hasPagePropCached( $title, 'newsectionlink' ) ||
		static::hasPagePropCached( $title, 'archivedtalk' )
	) &&
	// excluding the main namespace, unless it has been configured for signatures
	(
		!$title->inNamespace( NS_MAIN ) ||
		$services->getNamespaceInfo()->wantSignatures( $title->getNamespace() )
	)
);

The current logic means enhancements are available on most talk pages, and can be added to more with __NEWSECTIONLINK__ (excluding the main namespace).

For phase 1 we have decided this will be an MW JobQueue triggered by article edits.

Ready for deployment.

In T424606#12091817, @ppelberg wrote:

Resulting question: as a first step, why wouldn't we defer to volunteers to adjust the addReference config?

In T431375#12106033, @bmartinezcalvo wrote:

@Esanders the unified cards look good. Just an observation about the copy. The copy Indicated by an editor feels too generic. What about one of the following alternatives?

• "Flagged by another editor"
• "Reported by another editor"

Also, should we include the date it was flagged?

I'm also now looking into using lightpanda.io. Early experiments are showing a 80-90% drop in CPU/memory usage which is very promising.

In T431375#12106033, @bmartinezcalvo wrote:

@Esanders the unified cards look good. Just an observation about the copy. The copy Indicated by an editor feels too generic. What about one of the following alternatives?

• "Flagged by another editor"
• "Reported by another editor"

Also, should we include the date it was flagged?

Gemini suggests:

'--disable-gpu',               // Disables GPU hardware acceleration
'--disable-software-rasterizer',// Prevents CPU from trying to mimic a GPU
'--disable-dev-shm-usage',     // Prevents resource crunch in Docker container /dev/shm
'--no-sandbox',                // Usually necessary in Linux server environments
// Disable Blink Features & Extensions:
'--disable-extensions',
'--disable-component-extensions-with-background-pages',
'--disable-background-networking',
'--disable-sync',
'--metrics-recording-only',
'--disable-default-apps',
'--mute-audio',
'--no-first-run'

Block unnecessary network resources

await page.setRequestInterception(true);
page.on('request', (req) => {
  const resourceType = req.resourceType();
  if (['image', 'stylesheet', 'font', 'media'].includes(resourceType)) {
    req.abort();
  } else {
    req.continue();
  }
});

Yeah, here's the VE datamodel being told about <ref> in the Cite extension:

In T422431#12035427, @ppelberg wrote:

• Update mw:Edit_check/TextMatch#Configuration to include information about the functionality this ticket implements

@Esanders: can you please update the on-wiki documentation to include this new functionality?

Next steps are blocked on deployment (2026-07-16)

I went to store my patch in a local branch called paste-plain and I already had one from 2018 that tried to address this issue in roughly the same way:

I can reproduce in Chrome as well.