Disclaimer: I work for or provide services to the Wikimedia Foundation. However, the Foundation does not vet all my activity, so edits, statements, or other contributions made by this account may not reflect the views of the Foundation.
User Details
- User Since
- Oct 1 2015, 7:50 PM (556 w, 1 d)
- Availability
- Available
- IRC Nick
- Kemayo
- LDAP User
- DLynch
- MediaWiki User
- DLynch (WMF) [ Global Accounts ]
Yesterday
Here's an example of a template that adds a hidden category:
<link rel="mw:PageProp/Category" href="./Category:All_articles_with_unsourced_statements" about="#mwt5" typeof="mw:Transclusion" data-mw='{"parts":[{"template":{"target":{"wt":"Citation needed","href":"./Template:Citation_needed"},"params":{"date":{"wt":"January 2026"},"reason":{"wt":"There is conflicting information about when this album was released, as sources such as Amazon list the release date as 2001 instead of 2000. If one has a reliable source per WP:RSPS that says 2000, please cite it."}},"i":0}}]}' id="mwDQ"/><link rel="mw:PageProp/Category" href="./Category:Articles_with_unsourced_statements_from_January_2026" about="#mwt5"/><sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;" about="#mwt5" id="mwDg"><span typeof="mw:Entity">[</span><i><a rel="mw:WikiLink" href="./Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="There is conflicting information about when this album was released, as sources such as Amazon list the release date as 2001 instead of 2000. If one has a reliable source per WP:RSPS that says 2000, please cite it. (January 2026)">citation needed</span></a></i><span typeof="mw:Entity">]</span></sup>
One thing we could do is improve the documentation for this. I'm fairly sure this isn't highlighted anywhere as something a community might want to do.
I cannot reproduce this on a mac (where it's option-shift-space):
One more reproduction note: I cannot reproduce this when I have JS disabled.
Thu, May 28
Might be worth leaving the MinervaNeue tag on, just because it's significantly easier to trigger there, so there may be some relation.
@gh87 https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(WMF)?useformat=desktop&useparsoid=1&useskin=vector2022#Survey should get you that. It could be somewhat device-dependent, since the apparent error is RAM-exhaustion -- I'm testing it on an iPhone 17 pro, meaning there's 12GB of RAM.
Note that this does expose something currently sort-of private, which is exactly what content was thanked. The user was told this when the notification of the thanks arrived, but if they cleared that notification then it was no longer available to them.
Follow-up: I have done some DiscussionTools performance work on the above-mentioned ticket.
^ those patches take a local clone I made of the currently very-busy Village_Pump_(WMF), and reduce the time-cost of these areas of DiscussionTools during the initial page load from 176ms to 25ms. (On my high-spec macbook, so we can expect that to be more significant for many users.)
Did you try useformat=mobile&useskin=monobook ? That would help eliminate whether Minerva has anything to do with this.
Wed, May 27
As a variant of 1/2, we could make the existing showAsCheck and showAsSuggestion keys accept a config-object as well as just a boolean. We've already got precedent of doing nested config checks via textmatch rules, so a similar system could be used here. Check the top-level config, and then check whichever of the sub-configs are provided.
Connecting a cable didn't help as much as I had hoped. The main thing learned was that this isn't the page actually being stuck in a reload loop via navigation, but rather the rendering is crashing and restarting. I was also able to place breakpoints in Toggler.js which weren't reached (or at least, the process crashed regardless and things moved on -- hard to tell the difference).
Tue, May 26
I tested this on iOS.
Some debugging:
I'd have to assume it's something about the highlighting / auto-expansion code that's clashing, presumably in ways that're more noticeable on larger (and thus slower-to-load) pages.
Sat, May 23
Is this causing enough of a problem that we should backport the API fix on monday?
