MediaWiki talk:Rev-deleted-user

Broken on mobile

When this message appears on mobile, the parserfunctions aren't processed, so the raw wikitext is shown to the user. See for example [1]. --Yair rand (talk) 08:37, 17 May 2018 (UTC)[reply]

Protected edit request on 16 October 2023

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Replace content with "(Username or IP removed)".

This appears to be causing breakages in PageTriage code per T342409. Sohom (talk) 20:50, 16 October 2023 (UTC)[reply]

To expand a bit on the rationale, this is a widely used message and I really see no reason to have the server do a parser function based conditional wikitext render every time it encounters this message. If this conditional rendering of wikitext is important, this should be implemented in JS/at a MediaWiki level via a upstream patch, not at the wikitext level. Sohom (talk) 20:56, 16 October 2023 (UTC)[reply]

Done I disagree with the premise of this edit request - it should in theory be the responsibility of upstream software to support local customizations that predate it by years, not local customizations to give way to upstream software. But on the other hand it appears MediaWiki:Rev-deleted-user-contribs is displayed on Special:Contributions instead, so the condition can never be true, so I've removed it anyway. * Pppery * _{it has begun...} 00:05, 17 October 2023 (UTC)[reply]

I would tend to agree with you on most cases, but in the context of this message, there is absolutely no way for us to implement parsing this conditional at the JS level (where PageTriage is generally built) without having to resort to multiple API calls per render which would make PageTriage extremely slow to render, this edit request is a much more sane way of resolving the issue :) (imo) Thanks for implementing the change regardless :) Sohom (talk) 06:29, 17 October 2023 (UTC)[reply]